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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Bruce Momjian <bruce(at)momjian(dot)us>
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-19 00:48:55
Message-ID: 20200619004855.GA453547@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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.

> OK, I will work on that, thanks.

Thanks.
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2020-06-19 03:31:29 BUG #16504: Wrapping query in EXISTS() causes sequential scans of tables
Previous Message David Rowley 2020-06-19 00:16:52 Re: Problems at columns