From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Sergey Konoplev <gray(dot)ru(at)gmail(dot)com> |
Cc: | Wells Oliver <wellsoliver(at)gmail(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Upgrading from 9.1 to 9.2 - master AND slave |
Date: | 2013-07-16 09:58:55 |
Message-ID: | 20130716095855.GA28068@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Sun, Jul 14, 2013 at 09:31:16PM -0700, Sergey Konoplev wrote:
> On Wed, Jul 10, 2013 at 2:14 PM, Wells Oliver <wellsoliver(at)gmail(dot)com> wrote:
> > Following up to my earlier post: I have a master and a slave server (using
> > WAL), both 9.1. My 9.2 upgrade process is:
> >
> > 1) stop postgres on both servers
> > 2) run pg_upgrade --link on both servers
> > 3) change ports so 9.2 is on 5432, 9.1 on 5433
> > 4) restart
> >
> > Is this the best way to do it and ensure that the WAL is still being created
> > and the master/slave relationship properly maintained?
>
> The problem is that after pg_upgrade the system catalog on the servers
> wont match. Therefore you need to rebuild your slave from scratch.
>
> There were some ideas around rsync [1], however, nobody proved that
> they work appropriately.
>
> [1] http://www.postgresql.org/message-id/20120320204916.GB26163@momjian.us
Yes, though there was discussion about this at PGCon 2013 and I plan to
work on this for 9.4.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Emmanuel Massawe | 2013-07-16 12:37:20 | HOW TO TAKE POSTGRESQL GEONETWORK BACKUP WHEN SERVICE DOESNOT START |
Previous Message | Magnus Hagander | 2013-07-16 08:39:34 | Re: 777 permissions on basebackup directory |