Re: [DOC] Document concurrent index builds waiting on each other - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [DOC] Document concurrent index builds waiting on each other
Date
Msg-id 20200805021109.GA9079@alvherre.pgsql
Whole thread Raw
In response to Re: [DOC] Document concurrent index builds waiting on each other  (Andres Freund <andres@anarazel.de>)
Responses Re: [DOC] Document concurrent index builds waiting on each other  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On 2020-Mar-25, Andres Freund wrote:

> What I was thinking of was a new flag, with a distinct value from
> PROC_IN_VACUUM. It'd currently just be specified in the
> GetCurrentVirtualXIDs() calls in WaitForOlderSnapshots(). That'd avoid
> needing to wait for other CICs on different relations. Since CIC is not
> permitted on system tables, and CIC doesn't do DML on normal tables, it
> seems fairly obviously correct to exclude other CICs.

Hmm, that does work, and seems a pretty small patch -- attached.  Of
course, some more commentary is necessary, but the theory of operation
is as Andres says.  (It does not solve the vacuuming problem I was
describing in the other thread, only the spurious waiting that James is
complaining about in this thread.)

I'm going to try and poke holes on this now ... (Expression indexes with
falsely immutable functions?)

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment

pgsql-hackers by date:

Previous
From: James Coleman
Date:
Subject: Re: pg13dev: explain partial, parallel hashagg, and memory use
Next
From: Justin Pryzby
Date:
Subject: Re: pg13dev: explain partial, parallel hashagg, and memory use