Re: pg_upgrade and rsync

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-02 18:28:56
Message-ID: 20150302182856.GA17787@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Feb 24, 2015 at 12:13:17PM +0300, Vladimir Borodin wrote:
>
> 20 февр. 2015 г., в 18:21, Bruce Momjian <bruce(at)momjian(dot)us> написал(а):
>
> On Fri, Feb 20, 2015 at 09:45:08AM -0500, Bruce Momjian wrote:
>
> #3 bothered me as well because it was not specific enough. I like
> what
> you've added to clarify the procedure.
>
>
> Good. It took me a while to understand why they have to be in sync ---
> because we are using rsync in size-only-comparison mode, if they are
> not
> in sync we might update some files whose sizes changed, but not others,
> and the old slave would be broken. The new slave is going to get all
> new files or hard links for user files, so it would be fine, but we
> should be able to fall back to the old slaves, and having them in sync
> allows that.
>
>
> Also, since there was concern about the instructions, I am thinking of
> applying the patch only to head for 9.5, and then blog about it if
> people want to test it.
>
>
> Am I right that if you are using hot standby with both streaming replication
> and WAL shipping you do still need to take full backup of master after using
> pg_upgrade?

No, you would not need to take a full backup if you use these instructions.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ Everyone has their own god. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2015-03-02 18:37:10 Re: alter user/role CURRENT_USER
Previous Message Jan de Visser 2015-03-02 18:24:15 Re: Idea: closing the loop for "pg_ctl reload"