Re: First-draft release notes for back branches are up

From: Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: First-draft release notes for back branches are up
Date: 2020-11-07 23:10:32
Message-ID: 244fb8ff-ac08-7ea6-be20-d503ebffbd94@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 11/7/20 11:21 PM, Tom Lane wrote:
> Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> writes:
>> On 11/7/20 3:52 AM, Tom Lane wrote:
>>> Do you have some suggested text?
>
>> I think this might work:
>
> I dunno ... given that we have zero field reports, I doubt this is
> something we need to tell every BRIN user to do. The text I put in
> earlier today just recommends reindexing if you see the error.
>

Sorry, I haven't noticed you already wrote something :-( I agree it's
enough to recommend reindexing only when there's an error.

regards

--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2020-11-08 01:23:14 Yet another (minor) fix in BRIN
Previous Message Noah Misch 2020-11-07 22:46:06 Re: Rethinking LOCK TABLE's behavior on views