Re: client auth docs seem to have devolved - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: client auth docs seem to have devolved
Date
Msg-id CABUevEyd0VPGGy+6HS5O6ZGY7FmmqiC+B9BRG=VvwPK_5ieC0g@mail.gmail.com
Whole thread Raw
In response to Re: client auth docs seem to have devolved  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: client auth docs seem to have devolved  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: client auth docs seem to have devolved  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, Dec 17, 2019 at 5:01 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Magnus Hagander <magnus@hagander.net> writes:
> This was changed by Peter in
> commit 56811e57323faa453947eb82f007e323a952e1a1 along with the
> restructuring. It used to say "the following subsections". So techically I
> think that change is correct, but that doesn't necessarily make it helpful.

> But based on how it actually renders, since that section doesn't contain
> any actual useful info, we should perhaps just remove section 20.3
> completely. Peter, thoughts?

Then, URLs pointing to that page (such as Dave evidently has bookmarked)
would break entirely, which doesn't seem like an improvement.

Ugh, that's a good point of course. Didn't think of that.


I suggest changing the sect1's contents to be a list of available auth
methods, linked to their subsections.  That would provide approximately
the same quality-of-use as the subsection TOC that used to be there.

Yeah, that sounds better. Is there some docbook magic that can do that for us? 

--

pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: non-exclusive backup cleanup is mildly broken
Next
From: Tom Lane
Date:
Subject: Re: client auth docs seem to have devolved