Re: doc: BRIN indexes and autosummarize

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

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

To: Justin Pryzby <pryzby@telsasoft.com>

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

Date: 2022-07-06T07:45:31Z

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 2022-Jul-05, Justin Pryzby wrote:

> 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.

Hah, and I was wondering if "belongs in" was any better.

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

Roberto has some more substantive comments on the new text, so let's try
and fix everything together.  This time, I'll let you guys come up with
a new patch.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/