Re: [PATCH] updates to docs about HOT updates for BRIN - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [PATCH] updates to docs about HOT updates for BRIN
Date
Msg-id 202402271252.3pswvzjrmslu@alvherre.pgsql
Whole thread Raw
In response to Re: [PATCH] updates to docs about HOT updates for BRIN  (Stephen Frost <sfrost@snowman.net>)
Responses Re: [PATCH] updates to docs about HOT updates for BRIN
List pgsql-hackers
Hello,

On 2024-Feb-26, Stephen Frost wrote:

> Here's an updated patch which tries to improve on the wording a bit by
> having it be a bit more consistent.  Would certainly welcome feedback on
> it though, of course.  This is a tricky bit of language to write and
> a complex optimization to explain.

Should we try to explain what is a "summarizing" index is?  Right now
the only way to know is to look at the source code or attach a debugger
and see if IndexAmRoutine->amsummarizing is true.  Maybe we can just say
"currently the only in-core summarizing index is BRIN" somewhere in the
page.  (The patch's proposal to say "... such as BRIN" strikes me as too
vague.)

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/
"I am amazed at [the pgsql-sql] mailing list for the wonderful support, and
lack of hesitasion in answering a lost soul's question, I just wished the rest
of the mailing list could be like this."                               (Fotis)
              https://postgr.es/m/200606261359.k5QDxE2p004593@auth-smtp.hol.gr



pgsql-hackers by date:

Previous
From: Jelte Fennema-Nio
Date:
Subject: Re: libpq: PQfnumber overload for not null-terminated strings
Next
From: Dean Rasheed
Date:
Subject: Re: bug report: some issues about pg_15_stable(8fa4a1ac61189efffb8b851ee77e1bc87360c445)