Re: doc: BRIN indexes and autosummarize

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

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

To: Jaime Casanova <jcasanov@systemguards.com.ec>, Justin Pryzby <pryzby@telsasoft.com>

Cc: Roberto Mello <roberto.mello@gmail.com>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>

Date: 2022-07-05T11:47:27Z

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-04, Jaime Casanova wrote:

> I feel that somewhere in this paragraph it should be mentioned that is
> off by default.

OK, I added it.

On 2022-Jul-04, Justin Pryzby wrote:

> [ lots of comments ]

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

(Having almost-immediate doc refreshes is an enormous improvement.
Thanks Magnus.)

> Also, a reminder that this was never addressed (I wish the project had a way to
> keep track of known issues).
> 
> https://www.postgresql.org/message-id/20201113160007.GQ30691@telsasoft.com
> |error_severity of brin work item

Yeah, I've not forgotten that item.  I can't promise I'll get it fixed
soon, but it's on my list.

-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/
"Nunca se desea ardientemente lo que solo se desea por razón" (F. Alexandre)