On 05/23/2017 08:15 AM, Igor Neyman wrote:
-----Original Message-----
From: pgsql-general-owner@xxxxxxxxxxxxxx [mailto:pgsql-general-owner@xxxxxxxxxxxxxx] On Behalf Of Adrian Klaver
Sent: Tuesday, May 23, 2017 10:04 AM
To: pgsql-general@xxxxxxxxxxxxxx
Subject: Re: logical replication in PG10 BETA
On 05/23/2017 06:52 AM, Igor Neyman wrote:
sounds more like a SSL setup problem between the two Postgres servers, not really related to logical replication.
Can you try to setup the connections without SSL?
______________________________________________________________________
__________________________________
That's what I thought when I first saw this error.
But, I don't understand why is it trying to use sockets.
I have ssl=off in postgresql.conf on both sides.
AFAIK on Windows Postgres maps sockets to localhost.
Anyway that was why I was asking about your pg_hba.conf and PUBLICATION and SUBSCRIPTION settings, to see what is actually being requested?
Regards,
Igor
--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx
_________________________________________________________________________________________________________________
Interestingly, when I add this line to pg_hba.conf:
local all all md5
Postgres is not starting with the following error in the log file:
2017-05-23 11:02:10.397 EDT [4796] LOG: local connections are not supported by this build
2017-05-23 11:02:10.397 EDT [4796] CONTEXT: line 1 of configuration file "C:/PostgreSQL/10/data/pg_hba.conf"
2017-05-23 11:02:10.398 EDT [4796] FATAL: could not load pg_hba.conf
2017-05-23 11:02:10.403 EDT [4796] LOG: database system is shut down
The line I added is the first line.
" LOG: local connections are not supported by this build" - is this related to my problems with CREATE SUBSCRIPTION?
And another question:
Anyone from 2ndQuadrant could verify that pglogical included in the core PG10 BETA (packed by EnterpriseDB) supports Windows?
I think you are going to need to be more specific. I see pglogical as
the extension provided by 2ndQuadrant and builtin logical as provided by
the core server. If you are referring to the extension then see my post
upstream where I reference the pglogical issue that addresses this at
least partly.
Regards,
Igor
--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
