Re: documentation structure

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: documentation structure
Date: 2024-03-25 15:26:20
Message-ID: 7698f0d0-28a1-4f0c-a326-3d1e7d98dd95@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 22.03.24 14:59, Robert Haas wrote:
> And I don't believe that if someone were writing a physical book about
> PostgreSQL from scratch, they'd ever end up with a top-level chapter
> that looks anything like our GiST chapter. All of the index AM
> chapters are quite obviously clones of each other, and they're all
> quite short. Surely you'd make them sections within a chapter, not
> entire chapters.
>
> I do agree that PL/pgsql is more arguable. I can imagine somebody
> writing a book about PostgreSQL and choosing to make that topic into a
> whole chapter.

Yeah, I think there is probably a range of of things from pretty obvious
to mostly controversial.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2024-03-25 15:29:55 Re: pgsql: Track last_inactive_time in pg_replication_slots.
Previous Message Nathan Bossart 2024-03-25 15:21:21 Re: add AVX2 support to simd.h