From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | Elizabeth Christensen <elizabeth(dot)christensen(at)crunchydata(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: [PATCH] updates to docs about HOT updates for BRIN |
Date: | 2024-03-04 23:32:19 |
Message-ID: | 1abb9150e7e50eace9e6cd7520e22c7404856f3b.camel@j-davis.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 2024-02-27 at 09:48 -0500, Stephen Frost wrote:
> Attached is an updated patch which drops the 'such as' and adds a
> sentence mentioning that BRIN is the only in-core summarizing index.
The original patch reads more clearly to me. In v4, summarizing (the
exception) feels like it's dominating the description.
Also, is it standard practice to backport this kind of doc update? I
ordinarily wouldn't be inclined to do so, but v4 seems targeted at 16
as well.
Attached my own suggested wording that hopefully addresses Stephen and
Alvaro's concerns. I agree that it's tricky to write so I took a more
minimalist approach:
* I got rid of the "In summary" sentence because (a) it's confusing
now that we're talking about summarizing indexes; and (b) it's not
summarizing anything, it's just redundant.
* I removed the mention partial or expression indexes. It's a bit
redundant and doesn't seem especially helpful in this context.
If this is agreeable I can commit it.
Regards,
Jeff Davis
Attachment | Content-Type | Size |
---|---|---|
v5-0001-docs-Update-HOT-update-docs-for-19d8e2308b.patch | text/x-patch | 2.8 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Smith | 2024-03-05 00:40:27 | Re: Synchronizing slots from primary to standby |
Previous Message | Tom Lane | 2024-03-04 23:28:48 | Re: Avoid is possible a expensive function call (src/backend/utils/adt/varlena.c) |