From: | David Steele <david(at)pgmasters(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_upgrade and rsync |
Date: | 2015-02-20 02:35:02 |
Message-ID: | 54E69D56.5000901@pgmasters.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2/19/15 11:57 AM, Bruce Momjian wrote:
> On Wed, Jan 28, 2015 at 09:26:11PM -0800, Josh Berkus wrote:
>>
>> 3. Check that the replica is not very lagged. If it is, wait for
>> traffic to die down and for it to catch up.
>
> Now that 9.4.1 is released, I would like to get this doc patch applied
> --- it will close the often-requested feature of how to pg_upgrade slave
> clusters.
>
> I wasn't happy with Josh's specification above that the "replica is not
> very lagged", so I added a bullet point to check the pg_controldata
> output to verify that the primary and standby servers are synchronized.
>
> Yes, this adds even more complication to the pg_upgrade instructions,
> but it is really more of the same complexity. pg_upgrade really needs
> an install-aware and OS-aware tool on top of it to automate much of
> this.
#3 bothered me as well because it was not specific enough. I like what
you've added to clarify the procedure.
--
- David Steele
david(at)pgmasters(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-02-20 02:40:50 | Re: Exposing the stats snapshot timestamp to SQL |
Previous Message | Tomas Vondra | 2015-02-20 02:08:54 | Re: Exposing the stats snapshot timestamp to SQL |