Re: Shutdown Order with Primary/Standby?

From: Don Seiler <don(at)seiler(dot)us>
To: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
Cc: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Shutdown Order with Primary/Standby?
Date: 2017-08-11 14:10:44
Message-ID: CAHJZqBA36VdOrnBvMewjLTGtcjZ3BC+kvb7xWobuePk23GyHuA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Thu, Aug 10, 2017 at 1:13 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
wrote:

> Set keep wal segments to something largish (1000 or so) well before
> the upgrade etc. Make sure the volume holding pg_xlog can hold
> 1000*16MB of data. This ensures the streaming replicant can catch up
> if some stuff happens before it's back up.
>

If we have both primary and standby down at the same time, would this
really still be necessary? FWIW right now ours is set to keep 128.

Also, going back to my original question. Once both are down, is it best
practice to perform patching/upgrades on the standby first (starting
furthest downstream if cascading)? e.g. patch/upgrade the standby (via
standard CentOS7 yum from the repo), then start the standby DB and verify
nothing has broken, then do the same to the upstream or primary?

Don.

--
Don Seiler
www.seiler.us

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tang, Ronald K CIV FNMOC, N6 2017-08-11 16:00:27 Re: [Non-DoD Source] Re: Postgres user authentication with secure LDAP
Previous Message Günce Kaya 2017-08-11 09:01:24 Upgrading Postgresql Client