On Tue, Mar 3, 2015 at 11:38:58AM +0300, Vladimir Borodin wrote:
> No, you would not need to take a full backup if you use these instructions.
>
>
> Although it would be applied to documentation for 9.5 only, are these
> instructions applicable for upgrading from 9.3.6 to 9.4.1?
Yes. They work all the way back to 9.0.
> Following the instructions from patch I’ve got following errors in
> postgresql.log of replica after trying to start it with hot_standby = on:
>
> < 2015-02-24 11:47:22.861 MSK >WARNING: WAL was generated with wal_level=
> minimal, data may be missing
> < 2015-02-24 11:47:22.861 MSK >HINT: This happens if you temporarily set
> wal_level=minimal without taking a new base backup.
> < 2015-02-24 11:47:22.861 MSK >FATAL: hot standby is not possible because
> wal_level was not set to "hot_standby" or higher on the master server
> < 2015-02-24 11:47:22.861 MSK >HINT: Either set wal_level to "hot_standby" on
> the master, or turn off hot_standby here.
> < 2015-02-24 11:47:22.862 MSK >LOG: startup process (PID 28093) exited with
> exit code 1
> < 2015-02-24 11:47:22.862 MSK >LOG: aborting startup due to startup process
> failure
OK, hmmm. Thanks for testing. It feels like you didn't have your new
master set up for streaming replication when you ran pg_upgrade. Is
that correct? Should I specify that specifically in the instructions?
-- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB
http://enterprisedb.com
+ Everyone has their own god. +