This bug was fixed in the package postgresql-10 - 10.16-0ubuntu0.18.04.1
---------------
postgresql-10 (10.16-0ubuntu0.18.04.1) bionic; urgency=medium
* 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.
+ Details about this and many further changes can be found at:
https://www.postgresql.org/docs/10/static/release-10-16.html
-- Christian Ehrhardt <[email protected]> Wed, 10 Feb
2021 11:47:35 +0100
** Changed in: postgresql-10 (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915254
Title:
New upstream microreleases 9.5.25 10.16 12.6 13.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-13/+bug/1915254/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs