On Thu, Jul 1, 2010 at 1:02 PM, Tom Lane wrote:
> Fujii Masao writes:
>> Hmm... you'd like to get the system identifier from the postgres
>> server via SQL rather than starting replication? If so, you can do
>> that by adding replication entry into pg_hba.conf and performing the
>> following
>
>>
Fujii Masao writes:
> Hmm... you'd like to get the system identifier from the postgres
> server via SQL rather than starting replication? If so, you can do
> that by adding replication entry into pg_hba.conf and performing the
> following
> $ psql replication=1 -c "IDENTIFY_SYSTEM"
Cute, but
On Thu, Jul 1, 2010 at 11:35 AM, Zoid wrote:
> Hmm. I tried the replication=1 switch but I was prompted with the below but
> I noticed the "local" requirement assumes a UNIX socket which i'm not using.
> And both databases are actually on the same box (just different ports).
>
> psql: FATAL:
Hmm. I tried the replication=1 switch but I was prompted with the below
but I noticed the "local" requirement assumes a UNIX socket which i'm
not using. And both databases are actually on the same box (just
different ports).
psql: FATAL: no pg_hba.conf entry for replication connection fr
Zoid writes:
> Actually, I'm using postgresql beta2 and my replication process is
> connectiong to my primary (or backend) at 5432 via the connect_info line
> of the recovery.conf file.
> I had already saw that the error is identical if I merely connect
> directly to the primary and issue the
Tom,
Actually, I'm using postgresql beta2 and my replication process is
connectiong to my primary (or backend) at 5432 via the connect_info line
of the recovery.conf file.
I had already saw that the error is identical if I merely connect
directly to the primary and issue the command "IDENTIT
Zoid writes:
> Can anyone see why I keep getting the below "IDENTIFY_SYSTEM" error in
> my logs when I start my replication database process?
Are you sure the primary is 9.0? It sure looks like you're getting a
plain backend connection instead of a walsender, which is what I'd
expect to happen
Can anyone see why I keep getting the below "IDENTIFY_SYSTEM" error in
my logs when I start my replication database process?
I use "postgres primary" as my prefix in the syslog and "postgres
replication" as the replication one so their outputs are distinguishable.
Jun 30 14:10:25 postgres prim
Can anyone see why I keep getting the below "IDENTIFY_SYSTEM" error in
my logs when I start my replication database?
I use "postgres primary" as my prefix in the syslog and "postgres
replication" as the replication one.
Jun 30 14:10:25 postgres primary[19617]: [2-1] LOG: connection
received:
