| From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
|---|---|
| To: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: 2025-05-08 release announcement draft |
| Date: | 2025-05-07 01:38:28 |
| Message-ID: | 46eaf084-e0fd-42fe-af4e-528284433d89@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 5/6/25 8:29 AM, Matthias van de Meent wrote:
> On Tue, 6 May 2025 at 05:32, Jonathan S. Katz <jkatz(at)postgresql(dot)org> wrote:
>>
>> Hi,
>>
>> Attached is the draft of the release announcement for the 2025-05-08
>> release. Please review for correctness and omissions.
>>
>> Please provide feedback no later than 2025-05-08 12:00 UTC.
>
> I think this omits 459e7bf8e (aka 78cb2466f on REL_17_STABLE) which
> fixes certain bitmap scans' race condition with VACUUM. I think a line
> like the following could be good:
>
> * Fix for potentially incorrect results when bitmap scan nodes without
> output columns are run concurrently with VACUUM on the underlying
> table.
Added with some wordsmithing:
* Fix for potentially returning incorrect results when a bitmap scan
without output columns is executed while vacuum is also running on the
same table.
Jonathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2025-05-07 01:47:24 | Re: regdatabase |
| Previous Message | David G. Johnston | 2025-05-07 01:36:52 | Allow database owners to CREATE EVENT TRIGGER |