Date: Mon, 25 Mar 2024 13:07:52 +0100
From: hubert depesz lubaczewski <depesz@depesz.com>
Sender: depesz@depesz.com
To: James Pang <jamespang886@gmail.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: create index concurrently blocked by other query
Message-ID: <ZgFpGA4ymbed46B2@depesz.com>
Reply-To: depesz@depesz.com
References: 
 <CAHgTRfcE-LifnO81E2dTK4dKiUcSjqG0U=Gs5T_zAH=jUxJqGw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: 
 <CAHgTRfcE-LifnO81E2dTK4dKiUcSjqG0U=Gs5T_zAH=jUxJqGw@mail.gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/ZgFpGA4ymbed46B2%40depesz.com>
Precedence: bulk

On Sat, Mar 23, 2024 at 09:29:55PM +0800, James Pang wrote:
> Hi,
>     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. create index will continue its work as soon as all transactions
that are started than itself (the create index transaction) will end.

Best regards,

depesz