REINDEX and blocking SELECT queries

From: Satoshi Nagayasu <snaga(at)uptime(dot)jp>
To: pgsql-docs(at)postgresql(dot)org
Subject: REINDEX and blocking SELECT queries
Date: 2016-09-09 11:48:23
Message-ID: CAA8sozcK9eOo0Cj0ufBpAYi=oL2cJ-T9T7JN-_CqpYSWZ0GDcg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Hi all,

According to the manual, running REINDEX does not take any locks
on the parent table which block read operations.

> REINDEX locks out writes but not reads of the index's parent table.

REINDEX
https://www.postgresql.org/docs/9.5/static/sql-reindex.html

However, I heard some complains from a few people that this explanation
would lead some misunderstanding that REINDEX would not block
SELECT queries on the table.

Actually, REINDEX blocks SELECT queries, maybe in the planning phase.

This explanation is very critical for many people because they are planning
to run REINDEX online with believing in the explanation.

So, I think we should improve this explanation precisely not to lead
such misunderstanding.

What do you think? Any comments?

Regards,
--
Satoshi Nagayasu <snaga(at)uptime(dot)jp>

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Tom Lane 2016-09-09 13:41:36 Re: REINDEX and blocking SELECT queries
Previous Message chris+postgresql 2016-09-09 06:52:18 SET CONSTRAINTS ALL IMMEDIATE affects SET TRANSACTION READ ONLY