Re: [DOC] Document concurrent index builds waiting on each other

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: James Coleman <jtc331(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [DOC] Document concurrent index builds waiting on each other
Date: 2020-08-05 02:14:35
Message-ID: 20200805021435.GA9523@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2020-Aug-04, Alvaro Herrera wrote:

> diff --git a/src/include/storage/proc.h b/src/include/storage/proc.h
> index b20e2ad4f6..43c8ea3e31 100644
> --- a/src/include/storage/proc.h
> +++ b/src/include/storage/proc.h
> @@ -53,6 +53,8 @@ struct XidCache
> #define PROC_IS_AUTOVACUUM 0x01 /* is it an autovac worker? */
> #define PROC_IN_VACUUM 0x02 /* currently running lazy vacuum */
> #define PROC_IN_ANALYZE 0x04 /* currently running analyze */
> +#define PROC_IN_CIC 0x40 /* currently running CREATE INDEX
> + CONCURRENTLY */
> #define PROC_VACUUM_FOR_WRAPAROUND 0x08 /* set by autovac only */
> #define PROC_IN_LOGICAL_DECODING 0x10 /* currently doing logical
> * decoding outside xact */

Hah, missed to add new bit to PROC_VACUUM_STATE_MASK here.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2020-08-05 02:27:26 Re: pg13dev: explain partial, parallel hashagg, and memory use
Previous Message Justin Pryzby 2020-08-05 02:13:19 Re: pg13dev: explain partial, parallel hashagg, and memory use