| From: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Cc: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)postgresql(dot)org>, Josef Šimánek <josef(dot)simanek(at)gmail(dot)com> |
| Subject: | Re: pgsql: Ignore BRIN indexes when checking for HOT udpates |
| Date: | 2023-08-09 15:56:48 |
| Message-ID: | 486f389c-9306-23db-dbb5-5ffc3fec411d@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 8/9/23 11:11, Alvaro Herrera wrote:
> On 2021-Nov-30, Tomas Vondra wrote:
>
>> Ignore BRIN indexes when checking for HOT udpates
>
> I was trying to use RelationGetIndexAttrBitmap for something and
> realized that its header comment does not really explain things very
> well. That was already the case before this commit, but it (this
> commit) did add new possible values without mentioning them. I propose
> the attached comment-only patch.
>
+1
--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2023-08-09 17:24:04 | pgsql: doc: PG 16 relnotes, adjust \ef+ body comment to mention \sf |
| Previous Message | Bruce Momjian | 2023-08-09 15:16:53 | pgsql: doc: PG 16 relnotes, remove MAINTAIN item |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2023-08-09 16:05:42 | Re: Use of additional index columns in rows filtering |
| Previous Message | Peter Geoghegan | 2023-08-09 15:41:21 | Re: pg15: reltuples stuck at -1 after pg_upgrade and VACUUM |