On Fri, Jun 25, 2021 at 2:56 AM Bruce Momjian <br...@momjian.us> wrote:
>
> On Wed, Jun 23, 2021 at 07:45:53AM -0700, Peter Geoghegan wrote:
> > On Wed, Jun 23, 2021 at 5:50 AM Simon Riggs
> > <simon.ri...@enterprisedb.com> wrote:
> > > I just noticed that these commits are missing, yet are very important
> > > new features:
> > > d9d076222f5b94a8
> > > f9900df5f9
> > > c98763bf51bf
> > >
> > > These are important enough to be major features of PG14.
> >
> > I certainly think that they're important enough to be mentioned.
>
> OK, here is a doc patch to add a mention of this. I originally thought
> this was an optimization that wouldn't be of general interest.
Perhaps we should also add this text from the commit message to ensure
the importance is understood:
"This is extremely useful in cases where CIC/RC can run for a very long
time, because that used to be a significant headache for concurrent
vacuuming of other tables."
Proposed edits:
* "during certain index operations" -> "while concurrent index
operations run on other tables"
* spell Alvaro's name correctly
* "row expiration" is a term not currently used in PG docs, so we
should probably look for something else.
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.
--
Simon Riggs http://www.EnterpriseDB.com/
