pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedV9.4.0 standby server will not start
2+ messages / 2 participants
[nested] [flat]
* V9.4.0 standby server will not start
@ 2015-01-13 13:29 John Scalia <jayknowsunix@gmail.com>
2015-01-13 14:04 ` Re: V9.4.0 standby server will not start Devrim Gündüz <devrim@gunduz.org>
0 siblings, 1 reply; 2+ messages in thread
From: John Scalia @ 2015-01-13 13:29 UTC (permalink / raw)
To: pgsql-admin
Trying again,
Last Friday, I started setting up this new cluster, and I download the following 4 rpms from the postgresql site and the rhel-6.5-x86_64 directory, all were timestamped as 17 Dec 2014:
postgresql94-9.4.0-1PGDG.rhel6.x64_64.rpm
postgresql94-libs-9.4.0-1PGDG.rhel6.x64_64.rpm
postgresql94-server-9.4.0-1PGDG.rhel6.x86_64.rpm
postgresql94-contrib-9.4.0-1PGDG.rhel6.x86_64.rpm
My three servers are all CentOS 6.5 (virtualized). I went through all the server configuration files. These servers have been running V9.3.3 as a master with two standbys, and
V9.4.0 was installed alongside 9.3.3. The older version was stopped using "service postgresql-9.3 stop".
Modifications of postgresql.conf file were done in accordance with the instructions at https://wiki.postgresql.org/wiki/What%27s_new_in_PostgreSQL_9.4. The master server started
with no problems, and a replication slot called "standby_replication_slot_one" was created on it. I can see it via "select * from pg_replication_slots;". The standby servers were
then modified so that their recovery.conf file contained "primary_slotname = standby_replication_slot_one" it it. The recovery conf file originated and was operational for V9.3.3.
Only one slot currently exists and I have not started configuring for the second standby server. The first standby server fails to start using "service postgresql-9.4 start". The
postgresql-Mon.log shows:
#[root@csgha1] more postgresql-Mon.log
< 2015-01-12 12:07:15.543 @ > @FATAL: unrecognized recovery parameter "primary_slotname"
And that's the problem that I do not understand. Sorry to be so long winded, but I wanted to be thorough. Why is the standby throwing this error? It appears that the build is still
using an older parser, but I've verified that the whole thing is using 9.4 binaries.
--
Jay
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: V9.4.0 standby server will not start
2015-01-13 13:29 V9.4.0 standby server will not start John Scalia <jayknowsunix@gmail.com>
@ 2015-01-13 14:04 ` Devrim Gündüz <devrim@gunduz.org>
0 siblings, 0 replies; 2+ messages in thread
From: Devrim Gündüz @ 2015-01-13 14:04 UTC (permalink / raw)
To: John Scalia <jayknowsunix@gmail.com>; +Cc: pgsql-admin
Hi,
On Tue, 2015-01-13 at 08:29 -0500, John Scalia wrote:
> #[root@csgha1] more postgresql-Mon.log
> < 2015-01-12 12:07:15.543 @ > @FATAL: unrecognized recovery parameter "primary_slotname"
That parameter was renamed to primary_slot_name.
Regards,
--
Devrim GÜNDÜZ
Principal Systems Engineer @ EnterpriseDB: http://www.enterprisedb.com
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
Twitter: @DevrimGunduz , @DevrimGunduzTR
Attachments:
signature.asc (application/pgp-signature, 818B) download
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2015-01-13 14:04 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2015-01-13 13:29 V9.4.0 standby server will not start John Scalia <jayknowsunix@gmail.com>
2015-01-13 14:04 ` Devrim Gündüz <devrim@gunduz.org>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox