From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
---|---|
To: | Daniel Farina <daniel(at)heroku(dot)com> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Using pg_upgrade on log-shipping standby servers |
Date: | 2012-07-17 18:55:55 |
Message-ID: | 1342551355.22986.4.camel@sussancws0025 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 2012-07-17 at 01:02 -0700, Daniel Farina wrote:
> Could pg_upgrade emit WAL segment(s) to provide continuity of a
> timeline? So something like:
By "segments" did you mean "records"?
> * Take down the writable primary for pg_upgrade
> * Some WAL is emitted and possibly archived
> * The old version, when reaching the special pg_upgrade WAL, could
> exit or report its situation having paused replay (as clearly, it
> cannot proceed). Unsure.
I don't really understand this step.
> * Start up a new version of postgres on the same cluster at that
> point, which plays the upgrade-WAL.
>
> I see this being pretty mechanically intensive, but right now my hands
> are completely tied as to achieving total continuity of my archives,
> costing a base-backup's worth of risk window upon upgrade.
Does "continuity of archives" mean "avoid downtime" or "maintain a
single WAL sequence".
Regards,
Jeff Davis
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2012-07-17 20:28:32 | Re: isolation check takes a long time |
Previous Message | Peter Eisentraut | 2012-07-17 18:53:36 | Re: [COMMITTERS] pgsql: Split contrib documentation into extensions and programs |