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 from
host "[local]", user "postgres"
I've been using this to start the replication database processs, which
does start ok, spit out to syslog then barfs on the IDENTIFY_SYSTEM
returned from the primary.
/usr/local/pgsql/bin/postgres -p5433 -D replication_database -o -d5
Can I be sure that the Primary even has the capability to answer the
IDENTIFY_SYSTEM command? I'm beginning to think maybe this is zero'd
out until the beta is finalized. It would take a code search but if
the functionality is linked to Major Version and Minor version
variables, I guess its possible that it won't work until the beta2 is
normalized to an normal release. So I'll look for an alternate means
to extract the System Identity on the primary.
Tom Lane wrote:
Zoid <Zoid@xxxxxxxxxxxxx> 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 command "IDENTITY_SYSTEM", so it
seems to me the primary (or backend) is not treating the IDENTITY_SYSTEM
command as "Streaming Replication Protocol", but I'm not sure why it
would anyway as I've connected to thesame port psql does.
The port's not the issue --- replication connections are supposed to use
the same port. Try something like
psql -h primary-server replication=1
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
