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 <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1itvmY-0003B2-On
	for pgsql-docs@arkaria.postgresql.org; Tue, 21 Jan 2020 15:49:34 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1itvmX-00012B-8X
	for pgsql-docs@arkaria.postgresql.org; Tue, 21 Jan 2020 15:49:33 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1itvmW-000124-Tr
	for pgsql-docs@lists.postgresql.org; Tue, 21 Jan 2020 15:49:33 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1itvmR-0005fe-5e
	for pgsql-docs@lists.postgresql.org; Tue, 21 Jan 2020 15:49:31 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id 00LFnLn0020554;
	Tue, 21 Jan 2020 10:49:21 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
cc: Laurenz Albe <laurenz.albe@cybertec.at>,
        Simon Riggs <simon@2ndquadrant.com>,
        Ian Barwick <ian.barwick@2ndquadrant.com>,
        R Ransbottom <rirans@comcast.net>, Stephen Frost <sfrost@snowman.net>,
        pgsql-docs@lists.postgresql.org
Subject: Re: Documentation: 21.5. Default Roles
In-reply-to: <20200121150922.GB7084@momjian.us>
References: <20191227171654.GA2992@momjian.us>
 <8c2f4f1b90c993c8c6338b978a78a9ebbcd1c934.camel@cybertec.at>
 <20200114181331.GB10430@momjian.us>
 <20200114194502.GX3195@tamriel.snowman.net>
 <20200119035648.3k4d3erobborxwv3@rat.local>
 <957c35e3-8023-ebe6-3b51-3a620b66ae82@2ndquadrant.com>
 <20200120160258.GA28095@momjian.us>
 <CANP8+jJ7OcuGTgvk+S-fvWSj_KPjemV6vvhamj1g9zHuQx7a2A@mail.gmail.com>
 <20200120221357.GA28881@momjian.us>
 <dd9d5020fce3638efb69571f6f5577cbc82a8175.camel@cybertec.at>
 <20200121150922.GB7084@momjian.us>
Comments: In-reply-to Bruce Momjian <bruce@momjian.us>
	message dated "Tue, 21 Jan 2020 10:09:22 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <20552.1579621761.1@sss.pgh.pa.us>
Date: Tue, 21 Jan 2020 10:49:21 -0500
Message-ID: <20553.1579621761@sss.pgh.pa.us>
List-Id: <pgsql-docs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-docs@lists.postgresql.org>
List-Owner: <mailto:pgsql-docs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-docs>
Precedence: bulk

Bruce Momjian <bruce@momjian.us> writes:
> I looked at that option.  If the section was a hash reference,
> "#section_name", we could just add another hash, but in this case the
> section name is part of the file name:
> 	https://www.postgresql.org/docs/12/default-roles.html

Yeah, <sect1> IDs propagate into HTML page names.

> We can make that work in a backward-compatible way by changing the
> displayed section title, but not the file name.  I am not sure if that
> would confuse people though.

I think that's a really bad idea.

> We could also add a redirect at the web
> server level, but then you have to start to wonder whether the entire
> rename clarification is worth it for back branches.

Well, this is a question for the www list not here.  It might be a lot
easier for them to support a redirect that works the same across all
branches ... or then again, maybe not.  But we have to have a redirect,
else external links pointing at this page will be broken.

We have done page renames with redirects in the past, if memory serves,
so it's possible.  But I don't know details.

			regards, tom lane