Re: REINDEX blocks virtually any queries but some prepared queries.

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Frédéric Yhuel <frederic(dot)yhuel(at)dalibo(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: REINDEX blocks virtually any queries but some prepared queries.
Date: 2022-04-06 15:03:35
Message-ID: CAH2-Wz=6Fp=Z-GyCBcj4MJWPpYHQvNt+bh55FKQWdA=gGeW4eg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Apr 6, 2022 at 7:49 AM Frédéric Yhuel <frederic(dot)yhuel(at)dalibo(dot)com> wrote:
> From the documentation
> (https://www.postgresql.org/docs/current/sql-reindex.html#id-1.9.3.162.7),
> it sounds like REINDEX won't block read queries that don't need the
> index. But it seems like the planner wants to take an ACCESS SHARE lock
> on every indexes, regardless of the query, and so REINDEX actually
> blocks any queries but some prepared queries whose plan have been cached.
>
> I wonder if it is a bug, or if the documentation should be updated. What
> do you think?

I've always thought that the docs for REINDEX, while technically
accurate, are very misleading in practice.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2022-04-06 15:03:37 Re: Mingw task for Cirrus CI
Previous Message Andrew Dunstan 2022-04-06 14:58:38 Re: SQL/JSON: JSON_TABLE