pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <bruce@momjian.us>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Simon Riggs <simon.riggs@enterprisedb.com>
Cc: Robert Treat <rob@xzilla.net>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Erik Rijkers <er@xs4all.nl>
Cc: Justin Pryzby <pryzby@telsasoft.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: New docs chapter on Transaction Management and related changes
Date: Wed, 30 Nov 2022 08:52:23 -0500
Message-ID: <Y4dgF4CeFUY35U2T@momjian.us> (raw)
In-Reply-To: <c6304b19-6ff7-f3af-0148-cf7aa7e2fbfd@enterprisedb.com>
References: <CANbhV-E287+hqhEbC7vCShT16LKYM8aUhrvxQZdjX2osKAETkQ@mail.gmail.com>
	<Y0m9tIrlMqaA9dwP@momjian.us>
	<CAJSLCQ32vZ8S+yFbO1bKbKT=JE8Q6oRJXeRqfN6Atk-XJKPr7g@mail.gmail.com>
	<Y0tZf7N+cUJ9ebPI@momjian.us>
	<80a5fd9c080d66e62f90c9565e3e1b54e61f584c.camel@cybertec.at>
	<CANbhV-GafnnLmyMmjwYGFFcspk_twoEO56M3jiB7D0p_TkUmZA@mail.gmail.com>
	<3603e6e85544daa5300c7106c31bc52673711cd0.camel@cybertec.at>
	<Y3fY9nDysfSayXLJ@momjian.us>
	<Y4a3I+sKKoXlylpt@momjian.us>
	<c6304b19-6ff7-f3af-0148-cf7aa7e2fbfd@enterprisedb.com>

On Wed, Nov 30, 2022 at 07:33:44AM +0100, Peter Eisentraut wrote:
> On 30.11.22 02:51, Bruce Momjian wrote:
> > Patch applied back to PG 11.  Thanks to Simon for getting this important
> > information in our docs, and for the valuable feedback from others that
> > made this even better.
> 
> I request that the backpatching of this be reverted.  We don't want to have
> major chapter numbers in the documentation changing between minor releases.

Uh, how do others feel about this?  I wanted to get this information to
all our supported releases as soon as possible, rather than waiting for
PG 16 and for people to upgrade.  To me it seems the chapter renumbering
is worth that benefit.

I could put the new chapter inside an existing numbered section in the
back branches if people prefer that, but then PG 16 would have it in a
different place, which seems bad.

> More generally, major documentation additions shouldn't be backpatched, for
> the same reasons we don't backpatch features.

I don't see how documentation additions and feature additions are
comparable.  Feature additions change the behavior of the system, and
potentially introduce application breakage and bugs, while documentation
additions, if they apply to the supported version, have no such risks.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

Embrace your flaws.  They make you human, rather than perfect,
which you will never be.





view thread (68+ messages)  latest in thread

Message-ID: <Y4dgF4CeFUY35U2T@momjian.us>
Permalink:  ../Y4dgF4CeFUY35U2T@momjian.us/
Also on:    postgresql.org/message-id/Y4dgF4CeFUY35U2T@momjian.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: bruce@momjian.us, peter.eisentraut@enterprisedb.com, laurenz.albe@cybertec.at, simon.riggs@enterprisedb.com, rob@xzilla.net, alvherre@alvh.no-ip.org, er@xs4all.nl, pryzby@telsasoft.com
  Subject: Re: New docs chapter on Transaction Management and related changes
  In-Reply-To: <Y4dgF4CeFUY35U2T@momjian.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox