From: Bruce Momjian <bruce@momjian.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Jeff Janes <jeff.janes@gmail.com>
Cc: ram.maurya@lavainternational.in, pgsql-bugs <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #16497: old and new pg_controldata WAL segment sizes are invalid or do not match
Date: Sat, 27 Jun 2020 17:26:10 -0400
Message-ID: <20200627212610.GJ16644@momjian.us> (raw)
In-Reply-To: <20200619004855.GA453547@paquier.xyz>
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>
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 <bruce@momjian.us> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
Attachments:wal_level.diff (text/x-diff, 819B) downloaddiff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgmlindex 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;
<quote>Latest checkpoint location</quote> 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 <varname>wal_level</varname> to- <literal>replica</literal> in the <filename>postgresql.conf</filename> file on the+ Also, make sure <varname>wal_level</varname> is not set to + <literal>minimal</literal> in the <filename>postgresql.conf</filename> file on the
new primary cluster.
</para>
</step>
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-bugs@postgresql.org
Cc: bruce@momjian.us, michael@paquier.xyz, sfrost@snowman.net, tgl@sss.pgh.pa.us, jeff.janes@gmail.com
Subject: Re: BUG #16497: old and new pg_controldata WAL segment sizes are invalid or do not match
In-Reply-To: <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> <20200627212610.GJ16644@momjian.us>
* 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