From: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
---|---|
To: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: 2023-11-09 release announcement draft |
Date: | 2023-11-07 13:14:10 |
Message-ID: | CAEze2Wi2GBo1pMQY8356Czxc7bsxF5+jY4cMUk4aYddp_xdL1A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 6 Nov 2023 at 23:04, Jonathan S. Katz <jkatz(at)postgresql(dot)org> wrote:
>
> Hi,
>
> Attached is the release announcement draft for the 2023-11-09 release
> (16.1 et al.).
>
> Please review for accuracy and notable omissions. Please have all
> feedback in by 2023-11-09 08:00 UTC at the latest (albeit the sooner the
> better).
> 20231109updaterelease.md
> [...]
> * Provide more efficient indexing of `date`, `timestamptz`, and `timestamp`
> values in BRIN indexes. While not required, we recommend
> [reindexing](https://www.postgresql.org/docs/current/sql-reindex.html) BRIN
> indexes that include these data types after installing this update.
As the type's minmax_multi opclasses are marked as default, I believe
it makes sense to explicitly mention that only indexes that use the
type's minmax_multi opclasses would need to be reindexed for them to
see improved performance. The types' *_bloom and *_minmax opclasses
were not affected and therefore do not need to be reindexed.
Kind regards,
Matthias van de meent.
From | Date | Subject | |
---|---|---|---|
Next Message | jacktby jacktby | 2023-11-07 13:28:12 | Buffer Cache Problem |
Previous Message | Alexander Lakhin | 2023-11-07 13:00:00 | Re: collect_corrupt_items_vacuum.patch |