Re: doc: BRIN indexes and autosummarize

Justin Pryzby <pryzby@telsasoft.com>

From: Justin Pryzby <pryzby@telsasoft.com>

To: Alvaro Herrera <alvherre@alvh.no-ip.org>

Cc: Jaime Casanova <jcasanov@systemguards.com.ec>, Roberto Mello <roberto.mello@gmail.com>, pgsql-hackers@lists.postgresql.org

Date: 2022-07-05T19:58:38Z

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

On Tue, Jul 05, 2022 at 01:47:27PM +0200, Alvaro Herrera wrote:
> OK, I have adopted all your proposed changes, thanks for submitting in
> both forms.  I did some more wordsmithing and pushed, to branches 12 and
> up.  11 fails 'make check', I think for lack of Docbook id tags, and I
> didn't want to waste more time.  Kindly re-read the result and let me
> know if I left something unaddressed, or made something worse.  The
> updated text is already visible in the website:
> https://www.postgresql.org/docs/devel/brin-intro.html

One issue:

+   summarized range, the range that the new page belongs into
+   does not automatically acquire a summary tuple;

"belongs into" sounds wrong - "belongs to" is better.

I'll put that change into my "typos" branch to fix later if it's not addressed
in this thread.

-- 
Justin