From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | 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:09:22 |
Message-ID: | 20200121150922.GB7084@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Tue, Jan 21, 2020 at 10:06:43AM +0100, Laurenz Albe wrote:
> On Mon, 2020-01-20 at 17:13 -0500, Bruce Momjian wrote:
> > Well, I am renaming the documentation label for the feature. Is that
> > different than wording? I guess I can see that. If everyone agrees I
> > can revert the backpatch, but I don't want to do that if other people
> > are going to say this should be backpatched.
>
> I for one think that it should be backpatched, as long as the
> old link keeps working.
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
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. 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.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-01-21 15:49:21 | Re: Documentation: 21.5. Default Roles |
Previous Message | Vladimir Svedov | 2020-01-21 11:08:02 | Re: not clear what it means |