Re: BUG #16497: old and new pg_controldata WAL segment sizes are invalid or do not match - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: BUG #16497: old and new pg_controldata WAL segment sizes are invalid or do not match
Date
Msg-id 20200630155616.GB28710@momjian.us
Whole thread Raw
In response to Re: BUG #16497: old and new pg_controldata WAL segment sizes areinvalid or do not match  (Bruce Momjian <bruce@momjian.us>)
List 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@momjian.us>        https://momjian.us
  EnterpriseDB                             https://enterprisedb.com

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




pgsql-bugs by date:

Previous
From: Jehan-Guillaume de Rorthais
Date:
Subject: [BUG][PATCH] ecpg crash with bytea type and cursors
Next
From: PG Bug reporting form
Date:
Subject: BUG #16518: DBA on several PostgreSQL versions