doc: BRIN indexes and autosummarize
Roberto Mello <roberto.mello@gmail.com>
From: Roberto Mello <roberto.mello@gmail.com>
To: PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2022-06-28T23:22:34Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
BRIN: improve documentation on summarization
- e5085fc94724 15.0 landed
- d2323570ad33 13.8 landed
- 7c2b79c2bc22 12.12 landed
- 5001b44b1138 16.0 landed
- 0b71e43c4892 14.5 landed
Attachments
- brin-autosummarize-docs.patch (application/octet-stream) patch
Here's a patch to clarify the BRIN indexes documentation, particularly with
regards
to autosummarize, vacuum and autovacuum. It basically breaks down a big
blob of a
paragraph into multiple paragraphs for clarity, plus explicitly tells how
summarization
happens manually or automatically.
I also added cross-references to various relevant sections, including the
create index
page.
On this topic... I'm not familiar with with the internals of BRIN indexes
and in
backend/access/common/reloptions.c I see:
{
"autosummarize",
"Enables automatic summarization on this BRIN index",
RELOPT_KIND_BRIN,
AccessExclusiveLock
},
Is the exclusive lock on the index why autosummarize is off by default?
What would be the downside (if any) of having autosummarize=on by default?
Roberto
--
Crunchy Data - passion for open source PostgreSQL