pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ray Stell <stellr@vt.edu>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: standby upgrade questions
Date: Tue, 17 Oct 2017 11:34:51 -0400
Message-ID: <700537e7-9039-0bbd-61fb-b28af635121e@vt.edu> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

From: https://www.postgresql.org/docs/9.6/static/pgupgrade.html

Q1 - Is there a procedure to force this "catch up?"   I suppose 
preventing db activity with a pg_hba hack and running "select 
pg_switch_xlog()."   Maybe there's a better way?

 1.

    Prepare for standby server upgrades

    If you are upgrading standby servers (as outlined in sectionstep 10
    <https://www.postgresql.org/docs/9.6/static/pgupgrade.html#PGUPGRADE-STEP-REPLICAS;),
    verify that the old standby servers are caught up by
    runningpg_controldataagainst the old primary and standby clusters.
    Verify that the"Latest checkpoint location"values match in all
    clusters. (There will be a mismatch if old standby servers were shut
    down before the old primary.)

    Also, if upgrading standby servers, changewal_leveltoreplicain
    thepostgresql.conffile on the new master cluster.


Q2 - I was wondering what the end result is, in general, of this rsync 
of old and new? If the old db files and upgraded, new db files are 
meshed what do you get on the other side of the rsync?  Again, I mean in 
general what is the goal?

f. Runrsync

 From a directory that is above the old and new database cluster 
directories, run this for each slave:

rsync --archive --delete --hard-links --size-only old_pgdata new_pgdata remote_dir

whereold_pgdataandnew_pgdataare relative to the current directory, 
andremote_dirisabovethe old and new cluster directories on the standby 
server. The old and new relative cluster paths must match on the master 
and standby server.

view thread (2+ messages)  latest in thread

Message-ID: <700537e7-9039-0bbd-61fb-b28af635121e@vt.edu>
Permalink:  ../700537e7-9039-0bbd-61fb-b28af635121e@vt.edu/
Also on:    postgresql.org/message-id/700537e7-9039-0bbd-61fb-b28af635121e@vt.edu

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: stellr@vt.edu
  Subject: Re: standby upgrade questions
  In-Reply-To: <700537e7-9039-0bbd-61fb-b28af635121e@vt.edu>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox