Re: Release notes for February minor releases

From: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Michael Banck <michael(dot)banck(at)credativ(dot)de>
Subject: Re: Release notes for February minor releases
Date: 2022-02-06 22:30:34
Message-ID: bfd5a972-2ca8-880b-fcdf-8bb632cb0b54@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2/6/22 3:42 PM, Andres Freund wrote:
> Hi,
>
> On 2022-02-06 14:22:25 -0500, Jonathan S. Katz wrote:
>> On 2/6/22 1:44 PM, Andres Freund wrote:
>> I'm working on the release announcement and have been following this thread.
>>
>> Are there steps we can provide to help a user detect that this occurred,
>> even though it's a low-probability?
>
> Not realiably currently:
> https://postgr.es/m/20220205221742.qylnkze5ykc4mabv%40alap3.anarazel.de
> https://www.postgresql.org/message-id/20220204041935.gf4uwbdxddq6rffh@alap3.anarazel.de

Thanks.

For the release announcement then, it seems like the phrasing would to
indicate the probability of hitting this issue is low, but if you are
concerned, you should reindex.

I should have the first release announcement draft later tonight, which
I'll put on its usual separate thread.

Thanks,

Jonathan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Chapman Flack 2022-02-06 22:33:38 Re: GSoC 2022
Previous Message Andy Fan 2022-02-06 21:41:25 Re: Use generation context to speed up tuplesorts