From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Vladimir Borodin <root(at)simply(dot)name> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_upgrade and rsync |
Date: | 2015-03-03 15:01:19 |
Message-ID: | 20150303150119.GC5726@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Mar 3, 2015 at 04:55:56PM +0300, Vladimir Borodin wrote:
> 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?
>
>
> After running pg_upgrade I do put in new PGDATA on master old pg_hba.conf and
> postgresql.conf with wal_level = hot_standby. The full content of
> postgresql.conf could be seen here - http://pastie.org/9995902. Then I do rsync
> to replica, put recovery.conf and try to start both - first master, then
> replica. If I turn off hot_standby in replica configuration, it starts. What am
> I doing wrong?
After running initdb to create the new master, but before running
pg_upgrade, modify the new master's postgresql.conf and change wal_level
= hot_standby. (Don't modify pg_hba.conf at this stage.)
I didn't think that was necessary, but this might be some 9.3-specific
problem, but let's get it working first.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2015-03-03 15:08:33 | Re: Providing catalog view to pg_hba.conf file - Patch submission |
Previous Message | Tom Lane | 2015-03-03 14:39:03 | Re: autogenerated column names + views are a dump hazard |