Message-ID: <54B41751.2080707@gmail.com>
Date: Mon, 12 Jan 2015 13:49:53 -0500
From: John Scalia <jayknowsunix@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: 9.4.0 standby server will not start
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Hi all,

First off, if you receive a duplicate of this issue, it's due to my trying to send it originally through my verizon account, and it's held up waiting for permission. Also, I'd like 
to thank everyone for their assistance with my pg_upgrade issue over the weekend. I didn't get that resolved, but realized that for my purposes, I didn't really need the data.

Anyway, I've gotten my 9.4.0 primary server started and created a replication slot in it. It's called "standby_replication_slot_one" and I see it in the pg_replication_slots table. 
I'm now trying to get my first standby server running. I'm following the instructions at: https://wiki.postgresql.org/wiki/What%27s_new_in_PostgreSQL_9.4, but when I added the 
primary_slotname parameter to the recovery.conf file, the server complains that it isn't a valid parameter. I tried both setting it as its own parameter, and as setting as part of 
the primary_conninfo parameter just for grins. Neither succeeded although at least the server starts with the bad primary_conninfo setting, and I don't know why the system is 
complaining. Is there a typo in the instructions? Or do I need some extra settings to make this succeed?

Seems weird to me,
Jay


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin