Re: Documentation: 21.5. Default Roles
Bruce Momjian <bruce@momjian.us>
From: Bruce Momjian <bruce@momjian.us>
To: "Jonathan S. Katz" <jkatz@postgresql.org>
Cc: Magnus Hagander <magnus@hagander.net>, R Ransbottom <rirans@comcast.net>, Ian Barwick <ian.barwick@2ndquadrant.com>, Stephen Frost <sfrost@snowman.net>, Laurenz Albe <laurenz.albe@cybertec.at>, Pg Docs <pgsql-docs@lists.postgresql.org>
Date: 2020-02-06T05:11:31Z
Lists: pgsql-docs
On Tue, Feb 4, 2020 at 11:31:19AM -0500, Jonathan Katz wrote: > > Using this feature to handle the rename of a file *between* major > > versions, thus leaving the changes in master, should be safe (as long > > as we add an entry to that table in pgweb). > > > > As for back branches, I think we have to say that it's too close to > > the minor release to safely have something done in pgweb before then. > > This part I agree on, but let's sync offline to see if there is > something within reason, with a preference to *not* rush if we're > worried about breaking something right before release. Folks, is it Thursday. Can we revert this and return to it when we are not rushed? Alternatively, can someone who controls all the moving parts, like redirects and Stephen's patch additions take ownership of this issue, with authority to revert the patch if things are too close? -- Bruce Momjian <bruce@momjian.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 +
Commits
-
Rename Default Roles to Predefined Roles
- c9c41c7a337d 14.0 landed
-
Revert "docs: change "default role" wording to "predefined role""
- 608006c1b9c3 9.6.17 landed
- 994f9a71f826 10.12 landed
- 417d66c8b445 11.7 landed
- 2db27ff4eb3a 12.2 landed
- c185a57753e6 13.0 landed