| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
| Cc: | andrew(at)dunslane(dot)net, corey(dot)huinker(at)gmail(dot)com, jian(dot)universality(at)gmail(dot)com, robertmhaas(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: documentation structure |
| Date: | 2024-07-19 04:07:20 |
| Message-ID: | CAKFQuwZhikLAfG9ntU-611adW0AnnPFJ_wx7Hy3Lb_v7M7x27Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jul 18, 2024 at 8:06 PM Tatsuo Ishii <ishii(at)postgresql(dot)org> wrote:
> > I'm opposed to having a separate file for every function. I think
> > breaking up func.sgml into one piece per sect1 is about right. If that
> > proves cumbersome still we can look at breaking it up further, but
> > let's start with that.
>
> That will create at least 30 func-xx.sgml files.
>
> t-ishii$ grep '<sect1' func.sgml|wc -l
> 30
>
> I am afraid that's too many?
>
>
The premise and the resultant number of files both seem reasonable to me.
I could get that number down to maybe 20 if pressed but I don't see any
benefit to doing so. I look at a page on the website that needs updating
then go open its source file. Nice and tidy.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Etsuro Fujita | 2024-07-19 05:01:54 | Re: d844cd75a and postgres_fdw |
| Previous Message | Alexander Lakhin | 2024-07-19 04:00:01 | Re: Should consider materializing the cheapest inner path in consider_parallel_nestloop() |