From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | Re: pgsql: doc: clarify hierarchy of objects: global, db, schema, etc. |
Date: | 2020-04-02 21:29:15 |
Message-ID: | 20200402212915.GB7251@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
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(at)nuna(dot)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(at)momjian(dot)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 +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2020-04-02 21:32:33 | Re: pgsql: doc: adjust UPDATE/DELETE's FROM/USING to match SELECT's FROM |
Previous Message | Bruce Momjian | 2020-04-02 21:27:53 | Re: pgsql: doc: remove mention of bitwise operators as solely type-limited |