From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Peter Smith <smithpb2250(at)gmail(dot)com> |
Cc: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, vignesh C <vignesh21(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: [DOCS] Stats views and functions not in order? |
Date: | 2023-02-01 09:26:34 |
Message-ID: | 20230201092634.fpemltru6igv2ndm@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2023-Jan-30, Peter Smith wrote:
> On Fri, Jan 27, 2023 at 10:30 PM Peter Eisentraut
> <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
> > We could change the chunking boundary to be sect2 globally. This is
> > easily configurable (chunk.section.depth).
> > Thinking about it now, maybe this is what we need. As the documentation
> > grows, as it clearly does, the depth of the structure increases and
> > pages get longer. This can also be seen in other chapters.
> This chunk configuration idea sounds a better approach. If somebody
> else wants to champion that change separately then I can maybe help to
> review it.
Changing the chunking depth will change every single doc URL, though, so
the website will need some work to ensure there's a good transition
mechanism for the "this page in older/newer versions" functionality.
It sounds doable, but someone will need to craft it and test it. (Maybe
it would work to populate a table with all URLs at each side of the
divide, and its equivalent at the other side.)
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Nikolay Shaplov | 2023-02-01 09:27:10 | Re: [PATCH] New [relation] option engine |
Previous Message | Alvaro Herrera | 2023-02-01 09:04:26 | Re: [PATCH] New [relation] option engine |