pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Greg Clough <Greg.Clough@ihsmarkit.com>
To: Mariel Cherkassky <mariel.cherkassky@gmail.com>
To: PostgreSQL mailing lists <pgsql-performance@postgresql.org>
Subject: RE: upgrade to PG11 on secondary fails (no initdb was launched)
Date: Thu, 23 May 2019 11:23:47 +0000
Message-ID: <BYAPR12MB2999E06D968654BBBEC0F9DFEC010@BYAPR12MB2999.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CA+t6e1k-xEkjhUTnLik8MCf7-Sb+ek71jsZVN0ewduLEBy0iPw@mail.gmail.com>
References: <CA+t6e1nixp7tqTS3m1tV+XxC45gL8XG6JtSt5QdLYwBTCW3WmA@mail.gmail.com>
	<CA+t6e1k-xEkjhUTnLik8MCf7-Sb+ek71jsZVN0ewduLEBy0iPw@mail.gmail.com>

> 2019-05-23 04:17:02 EDT  23593  DETAIL:  The database cluster was initialized with PG_CONTROL_VERSION 960, but the server was compiled with PG_CONTROL_VERSION 1100.

It appears that you have not upgraded the standby server, so either use "rsync" or simply destroy and rebuild it from scratch "repmgr standby clone..."

      https://www.postgresql.org/docs/11/pgupgrade.html

      Upgrade Streaming Replication and Log-Shipping standby servers

      If you used link mode and have Streaming Replication (see Section 26.2.5) or Log-Shipping (see Section 26.2) standby servers, you can follow these steps to quickly upgrade them. You will not be running pg_upgrade on the standby servers, but rather rsync on the primary. Do not start any servers yet.

      If you did not use link mode, do not have or do not want to use rsync, or want an easier solution, skip the instructions in this section and simply recreate the standby servers once pg_upgrade completes and the new primary is running.

Greg.





________________________________

This e-mail, including accompanying communications and attachments, is strictly confidential and only for the intended recipient. Any retention, use or disclosure not expressly authorised by IHSMarkit is prohibited. This email is subject to all waivers and other terms at the following link: https://ihsmarkit.com/Legal/EmailDisclaimer.html

Please visit www.ihsmarkit.com/about/contact-us.html for contact information on our offices worldwide.


view thread (13+ messages)  latest in thread

Message-ID: <BYAPR12MB2999E06D968654BBBEC0F9DFEC010@BYAPR12MB2999.namprd12.prod.outlook.com>
Permalink:  ../BYAPR12MB2999E06D968654BBBEC0F9DFEC010@BYAPR12MB2999.namprd12.prod.outlook.com/
Also on:    postgresql.org/message-id/BYAPR12MB2999E06D968654BBBEC0F9DFEC010@BYAPR12MB2999.namprd12.prod.outlook.com

 · 

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-performance@postgresql.org
  Cc: Greg.Clough@ihsmarkit.com, mariel.cherkassky@gmail.com
  Subject: RE: upgrade to PG11 on secondary fails (no initdb was launched)
  In-Reply-To: <BYAPR12MB2999E06D968654BBBEC0F9DFEC010@BYAPR12MB2999.namprd12.prod.outlook.com>

* 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