Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jpIL4-0001iL-H8 for pgsql-bugs@arkaria.postgresql.org; Sat, 27 Jun 2020 21:26:18 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jpIL3-0000ZG-DV for pgsql-bugs@arkaria.postgresql.org; Sat, 27 Jun 2020 21:26:17 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jpIL3-0000WE-7V for pgsql-bugs@lists.postgresql.org; Sat, 27 Jun 2020 21:26:17 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jpIL1-0004yD-4I for pgsql-bugs@lists.postgresql.org; Sat, 27 Jun 2020 21:26:16 +0000 Received: from bruce by momjian.us with local (Exim 4.92) (envelope-from ) id 1jpIKw-0001xk-Mx; Sat, 27 Jun 2020 17:26:10 -0400 Date: Sat, 27 Jun 2020 17:26:10 -0400 From: Bruce Momjian To: Michael Paquier Cc: Stephen Frost , Tom Lane , Jeff Janes , ram.maurya@lavainternational.in, pgsql-bugs Subject: Re: BUG #16497: old and new pg_controldata WAL segment sizes are invalid or do not match Message-ID: <20200627212610.GJ16644@momjian.us> References: <20200618152911.GF7349@momjian.us> <20200618154152.GB6680@tamriel.snowman.net> <20200618154854.GG7349@momjian.us> <20200618155537.GC6680@tamriel.snowman.net> <20200618163615.GI7349@momjian.us> <20200618174241.GD6680@tamriel.snowman.net> <20200618180058.GK7349@momjian.us> <20200618181114.GG6680@tamriel.snowman.net> <20200618182943.GL7349@momjian.us> <20200619004855.GA453547@paquier.xyz> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="JYK4vJDZwFMowpUq" Content-Disposition: inline In-Reply-To: <20200619004855.GA453547@paquier.xyz> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --JYK4vJDZwFMowpUq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Jun 19, 2020 at 09:48:55AM +0900, Michael Paquier wrote: > On Thu, Jun 18, 2020 at 02:29:43PM -0400, Bruce Momjian wrote: > > On Thu, Jun 18, 2020 at 02:11:14PM -0400, Stephen Frost wrote: > >> I do think the doc could probably say replica 'or higher'. > > +1. Sounds good to me to just use "or higher" here. The docs insist > on the concept of hierarchy for values of wal_level. Instead of mentioning a specific wal_level "or higher", I decided to just mention the WAL level _not_ to use; patch attached. -- Bruce Momjian https://momjian.us EnterpriseDB https://enterprisedb.com The usefulness of a cup is in its emptiness, Bruce Lee --JYK4vJDZwFMowpUq Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="wal_level.diff" diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml index 319d613296..6779a5bddc 100644 --- a/doc/src/sgml/ref/pgupgrade.sgml +++ b/doc/src/sgml/ref/pgupgrade.sgml @@ -360,8 +360,8 @@ NET STOP postgresql-&majorversion; Latest checkpoint location values match in all clusters. (There will be a mismatch if old standby servers were shut down before the old primary or if the old standby servers are still running.) - Also, change wal_level to - replica in the postgresql.conf file on the + Also, make sure wal_level is not set to + minimal in the postgresql.conf file on the new primary cluster. --JYK4vJDZwFMowpUq--