On Tue, May 24, 2016 at 09:23:27AM -0500, Jim Nasby wrote: > On 5/16/16 2:36 AM, Bruce Momjian wrote: > >Right. I am thinking of writing some docs about how to avoid downtime > >for upgrades of various types. > > If there's some magic sauce to shrink pg_upgrade downtime to near 0 I think > folks would be very interested in that. > > Outside of that scenario, I think what would be far more useful is > information on how to do seamless master/replica switchovers using tools > like pgBouncer or pgPool. That ability is useful *all* the time, not just > when upgrading. It makes it trivial to do OS-level maintenance, and if > you're using a form of logical replication it also makes it trivial to do > expensive database maintenance, such as cluster/vacuum full/reindex. I've > worked with a few clients that had that ability and it was a huge stress > reducer. As a bonus, an unplanned outage of the master becomes far less > stressful, because you already know exactly how to fail over.
pg_upgrade's runtime can't be decreased dramatically --- I wanted to document other methods like you described. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
