public inbox for [email protected]
help / color / mirror / Atom feedFrom: Tom Lane <[email protected]>
To: Bruce Momjian <[email protected]>
Cc: Laurenz Albe <[email protected]>
Cc: Simon Riggs <[email protected]>
Cc: Ian Barwick <[email protected]>
Cc: R Ransbottom <[email protected]>
Cc: Stephen Frost <[email protected]>
Cc: [email protected]
Subject: Re: Documentation: 21.5. Default Roles
Date: Tue, 21 Jan 2020 10:49:21 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<CANP8+jJ7OcuGTgvk+S-fvWSj_KPjemV6vvhamj1g9zHuQx7a2A@mail.gmail.com>
<[email protected]>
<[email protected]>
<[email protected]>
Bruce Momjian <[email protected]> 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
view thread (45+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: Documentation: 21.5. Default Roles
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox