From: hubert depesz lubaczewski <depesz@depesz.com>
To: James Pang <jamespang886@gmail.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: create index concurrently blocked by other query
Date: Mon, 25 Mar 2024 13:07:52 +0100
Message-ID: <ZgFpGA4ymbed46B2@depesz.com> (raw)
In-Reply-To: <CAHgTRfcE-LifnO81E2dTK4dKiUcSjqG0U=Gs5T_zAH=jUxJqGw@mail.gmail.com>
References: <CAHgTRfcE-LifnO81E2dTK4dKiUcSjqG0U=Gs5T_zAH=jUxJqGw@mail.gmail.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: depesz@depesz.com, jamespang886@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: create index concurrently blocked by other query
In-Reply-To: <ZgFpGA4ymbed46B2@depesz.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox