Thread: pgsql: doc: clarify hierarchy of objects: global, db, schema, etc.
doc: clarify hierarchy of objects: global, db, schema, etc. The previous wording was confusing because it wasn't in decreasing order and had to backtrack. Also clarify role/user wording. Reported-by: jbird@nuna.com Discussion: https://postgr.es/m/158057750885.1123.2806779262588618988@wrigleys.postgresql.org Backpatch-through: 9.5 Branch ------ REL_10_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/4bd53803ef73b43124693e4a96e973e9329b8361 Modified Files -------------- doc/src/sgml/ddl.sgml | 15 +++++++-------- doc/src/sgml/manage-ag.sgml | 16 +++++++--------- 2 files changed, 14 insertions(+), 17 deletions(-)
On 2020-04-01 00:10, Bruce Momjian wrote: > doc: clarify hierarchy of objects: global, db, schema, etc. > > The previous wording was confusing because it wasn't in decreasing order > and had to backtrack. Also clarify role/user wording. > > Reported-by: jbird@nuna.com > > Discussion: https://postgr.es/m/158057750885.1123.2806779262588618988@wrigleys.postgresql.org > > Backpatch-through: 9.5 I would like to register a vote against large-scale backpatching of documentation patches like this. It appears that your default mode is to backpatch all documentation changes where possible. I think documentation backpatching should be restricted to where the old text was actually wrong. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
On Thu, Apr 2, 2020 at 07:27:53AM +0200, Peter Eisentraut wrote: > On 2020-04-01 00:10, Bruce Momjian wrote: > > doc: clarify hierarchy of objects: global, db, schema, etc. > > > > The previous wording was confusing because it wasn't in decreasing order > > and had to backtrack. Also clarify role/user wording. > > > > Reported-by: jbird@nuna.com > > > > Discussion: https://postgr.es/m/158057750885.1123.2806779262588618988@wrigleys.postgresql.org > > > > Backpatch-through: 9.5 > > I would like to register a vote against large-scale backpatching of > documentation patches like this. It appears that your default mode is to > backpatch all documentation changes where possible. I think documentation > backpatching should be restricted to where the old text was actually wrong. I have felt like you do, but have been overruled many times. If you wish, you can try to get agreement _not_ to perform such backpatches. -- Bruce Momjian <bruce@momjian.us> https://momjian.us EnterpriseDB https://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +