From: Tom Lane <tgl@sss.pgh.pa.us>
To: James Pang <jamespang886@gmail.com>
cc: pgsql-admin@lists.postgresql.org
Subject: Re: create index concurrently blocked by other query
In-reply-to: 
 <CAHgTRfcE-LifnO81E2dTK4dKiUcSjqG0U=Gs5T_zAH=jUxJqGw@mail.gmail.com>
References: 
 <CAHgTRfcE-LifnO81E2dTK4dKiUcSjqG0U=Gs5T_zAH=jUxJqGw@mail.gmail.com>
Comments: In-reply-to James Pang <jamespang886@gmail.com>
	message dated "Sat, 23 Mar 2024 21:29:55 +0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1409588.1711211842.1@sss.pgh.pa.us>
Date: Sat, 23 Mar 2024 12:37:22 -0400
Message-ID: <1409589.1711211842@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1409589.1711211842%40sss.pgh.pa.us>
Precedence: bulk

James Pang <jamespang886@gmail.com> writes:
>     PGv14, it's a time range partition table, we first create index ... on
> ONLY parent table and it's done very fast, then we are doing "create index
> concurrently ... on  each partition table", then we saw it blocked by some
> other sessopm  "select on other tables" , is it expected ?

Yes, read the documentation.  CONCURRENTLY avoids blocking other
transactions, at the cost of being easily blocked itself.

			regards, tom lane