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 fro
Satoshi Nagayasu writes:
> According to the manual, running REINDEX does not take any locks
> on the parent table which block read operations.
> Actually, REINDEX blocks SELECT queries, maybe in the planning phase.
Hm. REINDEX does take out only ShareLock on the table, which would not
block DML,
On 09/09/2016 03:41 PM, Tom Lane wrote:
> Satoshi Nagayasu writes:
>> According to the manual, running REINDEX does not take any locks
>> on the parent table which block read operations.
>> Actually, REINDEX blocks SELECT queries, maybe in the planning phase.
>
> Hm. REINDEX does take out only S
2016-09-09 22:41 GMT+09:00 Tom Lane :
> Satoshi Nagayasu writes:
>> According to the manual, running REINDEX does not take any locks
>> on the parent table which block read operations.
>> Actually, REINDEX blocks SELECT queries, maybe in the planning phase.
>
> Hm. REINDEX does take out only Shar
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/9.1/static/sql-set-constraints.html
Description:
We found that normally, if you execute SET TRANSACTION READ ONLY, it
prevents COMMIT from happening if any data has been changed in the
transa
chris+postgre...@qwirx.com writes:
> We found that normally, if you execute SET TRANSACTION READ ONLY, it
> prevents COMMIT from happening if any data has been changed in the
> transaction (and we have been relying on this for safety).
This seems like a truly bizarre expectation.
I wouldn't reall
