Greetings, * Bruce Momjian (br...@momjian.us) wrote: > OK, Stephen, I believe you have a more comprehensive patch to make this > change. When can you complete it? The above email is from April.
Having gone back through this thread (again) to figure out where we are
on this, and chatting with Jonathan about the options that are available
through the web system, and trying to sort out my own feelings on what
makes the most sense here, I'd like to bring up a few points and a
proposal regarding the rename:
- General agreement that 'predefined' is better than 'default'
- Unclear on back-patching:
Voices in favor: Rob, Laurenz, Bruce
Voices against: Ian, Simon, Peter, Stephen
Having understood now a bit better what is possible with the web system,
many thanks to Jonathan for chatting with me about it, I'll try to
explain here what the options are:
- Change the back-branches and use the new feature ("doc page
redirects") to redirect old links to default-roles to
predefined-roles.
- Change the feature's name in v14, but create a "doc page alias" to
allow users viewing v13's "default roles" to see a v14 link which
would take them to "predefined roles".
I'll note that we've got a number of examples of "doc page aliases"
being used to handle name changes:
catalog-pg-replication-slots.html <-> view-pg-replication-slots.html
pgxlogdump.html <-> pgwaldump.html
app-pgresetxlog.html <-> app-pgresetwal.html
legalnotice.html <-> LEGALNOTICE.html
app-pgreceivexlog.html <-> app-pgreceivewal.html
I've also been thinking about the code change impact from this, as I do
think we should have the code and the documentation and general feature
naming be consistent, but that implies changing things like
DEFAULT_ROLE_MONITOR to be PREDEFINED_ROLE_MONITOR, potentially breaking
compilation of extensions that use those #define's (such as even our own
extensions like file_fdw do) in a minor version update, which doesn't
seem terribly nice to do.
Therefore, on the whole, the proposal that I would put out there is:
- Rename everything (code, docs, etc) to 'predefined roles' for v14+
- Update the documentation (only) in back-branches to mention that the
feature was renamed in v14 to 'predefined roles'
- Use the 'doc page alias' feature to make the documentation page for
'default roles' on the older versions link to 'predefined roles' in
the newer versions, and vice-versa
Thoughts?
Thanks,
Stephen
signature.asc
Description: PGP signature
