| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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-21 23:40:38 |
| Message-ID: | 743b27bd-0b21-41cd-8310-c8006bf08f94@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 21.03.24 15:31, Robert Haas wrote:
> On Thu, Mar 21, 2024 at 9:38 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I'd follow the extend.sgml precedent: have a file corresponding to the
>> chapter and containing any top-level text we need, then that includes
>> a file per sect1.
>
> OK, here's a new patch set. I've revised 0003 and 0004 to use this
> approach, and I've added a new 0005 that does essentially the same
> thing for the PL chapters.
I'm highly against this. If I want to read about PL/Python, why should
I have to wade through PL/Perl and PL/Tcl?
I think, abstractly, in a book, PL/Python should be a chapter of its
own. Just like GiST should be a chapter of its own. Because they are
self-contained topics.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melih Mutlu | 2024-03-21 23:45:52 | Re: Flushing large data immediately in pqcomm |
| Previous Message | Vik Fearing | 2024-03-21 23:38:09 | Re: Catalog domain not-null constraints |