From: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
---|---|
To: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: HOT readme missing documentation on summarizing index handling |
Date: | 2023-07-07 17:06:35 |
Message-ID: | 546bf2c7-57a3-0d24-9ff5-b51f6fa03bce@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 7/7/23 18:34, Matthias van de Meent wrote:
> On Fri, 7 Jul 2023 at 00:14, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> wrote:
>>
>> Yeah, README.HOT should have been updated, and I see no reason not to
>> backpatch this to v16. Barring objections, I'll do that tomorrow.
>>
>> I have two suggesting regarding the README.HOT changes:
>>
>> 1) I'm not entirely sure it's very clear what "referential integrity of
>> indexes across tuple updates" actually means. I'm afraid "referential
>> integrity" may lead readers to think about foreign keys. Maybe it'd be
>> better to explain this is about having index pointers to the new tuple
>> version, etc.
>>
>> 2) Wouldn't it be good to make it a bit more explicit we now have three
>> "levels" of HOT:
>>
>> (a) no indexes need update
>> (b) update only summarizing indexes
>> (c) update all indexes
>>
>> The original text was really about on/off, and I'm not quite sure the
>> part about "exception" makes this very clear.
>
> Agreed on both points. Attached an updated version which incorporates
> your points.
>
Thanks, pushed after correcting a couple typos.
regards
--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Matthias van de Meent | 2023-07-07 17:12:31 | Re: HOT readme missing documentation on summarizing index handling |
Previous Message | Nathan Bossart | 2023-07-07 16:57:10 | Re: pgsql: Fix search_path to a safe value during maintenance operations. |