Re: New docs chapter on Transaction Management and related changes

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>, Robert Treat <rob(at)xzilla(dot)net>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Erik Rijkers <er(at)xs4all(dot)nl>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: New docs chapter on Transaction Management and related changes
Date: 2022-11-30 14:10:35
Message-ID: CAKFQuwZjMCjUkTB7+Cgy1bcu-c+teOPdNEMEn7FvhL_7WA5EcQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Nov 30, 2022 at 6:52 AM Bruce Momjian <bruce(at)momjian(dot)us> wrote:

> 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'd maybe accept having it back-patched to v15 on that basis but not any
further.

But I agree that our general behavior is to only apply this scope of update
of the documentation to HEAD.

David J.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Pyhalov 2022-11-30 14:30:45 Re: Partial aggregates pushdown
Previous Message Bruce Momjian 2022-11-30 13:55:14 Re: pg_dump bugs reported as pg_upgrade bugs