Re: BUG #16497: old and new pg_controldata WAL segment sizes are invalid or do not match

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, ram(dot)maurya(at)lavainternational(dot)in, pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #16497: old and new pg_controldata WAL segment sizes are invalid or do not match
Date: 2020-06-30 15:56:16
Message-ID: 20200630155616.GB28710@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sat, Jun 27, 2020 at 05:26:10PM -0400, Bruce Momjian wrote:
> 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.

Patch applied through 9.5.

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com

The usefulness of a cup is in its emptiness, Bruce Lee

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2020-06-30 16:09:58 BUG #16518: DBA on several PostgreSQL versions
Previous Message Jehan-Guillaume de Rorthais 2020-06-30 13:30:08 [BUG][PATCH] ecpg crash with bytea type and cursors