Re: PG 14 release notes, first draft

From: Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Peter Geoghegan <pg(at)bowt(dot)ie>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PG 14 release notes, first draft
Date: 2021-07-13 15:33:38
Message-ID: CANbhV-EXg-=_sc1W4HOx7uqND58bhRepfcD=ZpyC0nDrtJcHtw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jul 2, 2021 at 12:50 AM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
> On Thu, Jul 1, 2021 at 03:13:30PM +0100, Simon Riggs wrote:
> > On Wed, Jun 30, 2021 at 11:20 PM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> > > > * "row expiration" is a term not currently used in PG docs, so we
> > > > should probably look for something else.
> > >
> > > Yeah, I changed that to "removing dead rows" which seems to be our
> > > standard text.
> >
> > What you have now looks great for this feature, thanks.
>
> Good.
>
> > > > There are 2 important features here, so the 2nd feature is worth
> > > > mentioning also:
> > > >
> > > > Avoid spurious waits in concurrent indexing
> > > >
> > > > Previously, multiple concurrent index operations could deadlock or
> > > > cause long waits.
> > > > Waits are avoided except for indexes with expressions, or WHERE predicates.
> > >
> > > OK, I added text to the bottom to try and capture that; new patch
> > > attached, now with UTF8 encoding.
> >
> > The text from "This also avoids..." tries to explain this, but they
> > are two separate features, each important in its own right.
> >
> > So regrettably, this part doesn't capture it, for me.
>
> I see what you mean. This is in the VACUUM section, and this feature,
> though from the same commits, has nothing to do with vacuum. Attached
> is an updated patch.

Perfect, many thanks.

--
Simon Riggs http://www.EnterpriseDB.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2021-07-13 15:37:49 Re: DROP relation IF EXISTS Docs and Tests - Bug Fix
Previous Message vignesh C 2021-07-13 15:33:22 Re: Printing backtrace of postgres processes