Re: Documentation: 21.5. Default Roles

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Ian Barwick <ian(dot)barwick(at)2ndquadrant(dot)com>, R Ransbottom <rirans(at)comcast(dot)net>, Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: Documentation: 21.5. Default Roles
Date: 2020-01-21 15:49:21
Message-ID: 20553.1579621761@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Bruce Momjian <bruce(at)momjian(dot)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

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message R Ransbottom 2020-01-24 00:12:08 Re: Documentation: 21.5. Default Roles
Previous Message Bruce Momjian 2020-01-21 15:09:22 Re: Documentation: 21.5. Default Roles