* New upstream version (LP: #1915254)
+ Fix CREATE INDEX CONCURRENTLY to wait for
concurrent prepared transactions (Andrey Borodin)
At the point where CREATE INDEX CONCURRENTLY
waits for all concurrent transactions to complete so that it can see
rows they inserted, it must also wait for all prepared transactions
to complete, for the same reason. Its failure to do so meant that
rows inserted by prepared transactions might be omitted from the new
index, causing queries relying on the index to miss such rows.
In installations that have enabled prepared transactions
(max_prepared_transactions > 0),
it's recommended to reindex any concurrently-built indexes in
case this problem occurred when they were built.
This bug was fixed in the package postgresql-10 - 10.16-0ubuntu0. 18.04.1
--------------- 0ubuntu0. 18.04.1) bionic; urgency=medium
postgresql-10 (10.16-
* New upstream version (LP: #1915254)
+ Fix CREATE INDEX CONCURRENTLY to wait for
concurrent prepared transactions (Andrey Borodin)
At the point where CREATE INDEX CONCURRENTLY max_prepared_ transactions > 0),
waits for all concurrent transactions to complete so that it can see
rows they inserted, it must also wait for all prepared transactions
to complete, for the same reason. Its failure to do so meant that
rows inserted by prepared transactions might be omitted from the new
index, causing queries relying on the index to miss such rows.
In installations that have enabled prepared transactions
(
it's recommended to reindex any concurrently-built indexes in
case this problem occurred when they were built.
+ Details about this and many further changes can be found at: /www.postgresql .org/docs/ 10/static/ release- 10-16.html
https:/
-- Christian Ehrhardt <email address hidden> Wed, 10 Feb 2021 11:47:35 +0100