Обсуждение: 9.4.0 standby server will not start
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 realizedthat 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 bothsetting 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_conninfosetting, 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
Hi,
--
2015-01-12 19:49 GMT+01:00 John Scalia <jayknowsunix@gmail.com>:
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,
Seems weird to me too. Can you give us the actual, complete error message? btw, it's its own parameter.
--
On 1/12/2015 4:07 PM, Guillaume Lelarge wrote:
I will attempt to do so. The machine I normally send email to this account is not permitted to connect to Verizon's network. That's part of the reason I originally sent it via my Verizon system - I had copied the error message, etc. into that message. That message is probably on the postgresql.org server just awaiting permission to be sent out. Really, both that sender and myself are the same individual.
Hi,2015-01-12 19:49 GMT+01:00 John Scalia <jayknowsunix@gmail.com>: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,Seems weird to me too. Can you give us the actual, complete error message? btw, it's its own parameter.
I will attempt to do so. The machine I normally send email to this account is not permitted to connect to Verizon's network. That's part of the reason I originally sent it via my Verizon system - I had copied the error message, etc. into that message. That message is probably on the postgresql.org server just awaiting permission to be sent out. Really, both that sender and myself are the same individual.