Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ihIzo-0008SF-RV for pgsql-www@arkaria.postgresql.org; Tue, 17 Dec 2019 19:59:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ihIzn-0006WY-Kr for pgsql-www@arkaria.postgresql.org; Tue, 17 Dec 2019 19:59:03 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ihIzn-0006WR-Dl for pgsql-www@lists.postgresql.org; Tue, 17 Dec 2019 19:59:03 +0000 Received: from mail-lf1-x142.google.com ([2a00:1450:4864:20::142]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1ihIzk-0005Ox-HR for pgsql-www@postgresql.org; Tue, 17 Dec 2019 19:59:03 +0000 Received: by mail-lf1-x142.google.com with SMTP id y19so7850191lfl.9 for ; Tue, 17 Dec 2019 11:59:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hagander-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=tyftxqzy+QEX1/qLZREtWbagdbXkqYVgTnXt6uAyYpE=; b=C7carQhUW2zW4DbEDYZg56NZN8KqhhePop18paA9Es4As/MhlQcnk/ALsJjnAPk5iv v5dVQV3fVGghPVUHS4pHNHz9Bntl+7V8cAuXXVFETh2pAmge3tqq4eY/BEnh1v0ko3BR VS84mJoy6tP/LpSgv9qEHoir7/bG2OkdwGlK1z4nwRfSMrC8PvqxesQg5IPxgPwnxSCr pfQ5rTgV1Hqxa3QYXtU9Azm9gyuHeBZr705PdY7A6A7E6QX3YdBDTqSwrs+n82enaRr3 pOmArO7mIjIvNqDCTwOZYIlSHgZ6D3ru/terKU5wnZqRKHV6rSPzO+U7dbRQM1RskDPl 6Fzg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=tyftxqzy+QEX1/qLZREtWbagdbXkqYVgTnXt6uAyYpE=; b=kxeT1xU+8Gvi44It73T2ClvMC3eFvrUJSUPoFzNJcFvE+V8BQnHpjUDYsZSp2r/lCv L8gLpDACY3aXn6MzbgXC2pF66eGO7BGaBx6QOZrTPTx1JrFwKe6GKLu1zmtGxKxnAJEV zdQbfGuHbH5spefnw0OVvo5vi6kjfbAGQoxTowHgTfR8xF2VVnWOgnnmLUX4yN3R+hxY aeWyGRTcRrAB2xagtARpNHzdZaHjULqOuOlOmgcGai38YuNaDcdGrwBPVikYAJnYdvO8 IUDLYTh8OZh2J8sB8wefGZJw98Z8P3SQTRcrSDWb27Y5cBDSwujpbMrs7AINoQaW/ISv 6H8w== X-Gm-Message-State: APjAAAWa+KWk0kY0qZKtY5STS74wTKglW/XndZc/8Oh/c57KxF9cIGRz 4UD6YA0Y+9mz71yu3Oqp7tVTv7zCN6RyR0XLD4cl0A== X-Google-Smtp-Source: APXvYqzWlb7hvaf4EgO7dgBZ08z9MmDbDHR0/lgE04cnY/ODIo5x3itBj9MOgO4KFlI3EUp24cGtpty/E1zXkmd9mzQ= X-Received: by 2002:ac2:5388:: with SMTP id g8mr3792549lfh.43.1576612738445; Tue, 17 Dec 2019 11:58:58 -0800 (PST) MIME-Version: 1.0 References: <13336.1576598463@sss.pgh.pa.us> In-Reply-To: <13336.1576598463@sss.pgh.pa.us> From: Magnus Hagander Date: Tue, 17 Dec 2019 20:58:46 +0100 Message-ID: Subject: Re: client auth docs seem to have devolved To: Tom Lane Cc: Dave Cramer , Peter Eisentraut , PostgreSQL-development , PostgreSQL WWW Content-Type: multipart/alternative; boundary="0000000000003950b90599ebc2d2" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --0000000000003950b90599ebc2d2 Content-Type: text/plain; charset="UTF-8" On Tue, Dec 17, 2019 at 5:01 PM Tom Lane wrote: > Magnus Hagander 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? -- Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/ --0000000000003950b90599ebc2d2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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". S= o 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 c= ontain
> 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<= br> methods, linked to their subsections.=C2=A0 That would provide approximatel= y
the same quality-of-use as the subsection TOC that used to be there.

Yeah, that sounds better. Is there some docbo= ok magic that can do that for us?=C2=A0

--
=C2=A0Magnus= Hagander
=C2=A0Me: https://www.hagander.net/
=C2=A0Work: https://www.redpill-linpro.com/
=
--0000000000003950b90599ebc2d2--