[ubuntu/bionic-proposed] postgresql-10 10.16-0ubuntu0.18.04.1 (Accepted)
Christian Ehrhardt
christian.ehrhardt at canonical.com
Tue Feb 16 20:25:50 UTC 2021
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
Date: Wed, 10 Feb 2021 11:47:35 +0100
Changed-By: Christian Ehrhardt <christian.ehrhardt at canonical.com>
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
https://launchpad.net/ubuntu/+source/postgresql-10/10.16-0ubuntu0.18.04.1
-------------- next part --------------
Format: 1.8
Date: Wed, 10 Feb 2021 11:47:35 +0100
Source: postgresql-10
Architecture: source
Version: 10.16-0ubuntu0.18.04.1
Distribution: bionic
Urgency: medium
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Changed-By: Christian Ehrhardt <christian.ehrhardt at canonical.com>
Launchpad-Bugs-Fixed: 1915254
Changes:
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
Checksums-Sha1:
37ec7c3f1b589d5d062a0579098cad7cdb378aa2 3620 postgresql-10_10.16-0ubuntu0.18.04.1.dsc
594d7f1c604a9666499510d69b6dece97632a61d 19140221 postgresql-10_10.16.orig.tar.bz2
def6c0c6c2d9a3212bad4307625747ae18b99747 35524 postgresql-10_10.16-0ubuntu0.18.04.1.debian.tar.xz
b4c0f53035b92c807ae4be79298caafd46f1eea7 8238 postgresql-10_10.16-0ubuntu0.18.04.1_source.buildinfo
Checksums-Sha256:
0f792430fa27b1e3516061fa861d008bc0ed523729e61d6a6487c4e200017bf9 3620 postgresql-10_10.16-0ubuntu0.18.04.1.dsc
a35c718b1b6690e01c69626d467edb933784f8d1d6741e21fe6cce0738467bb3 19140221 postgresql-10_10.16.orig.tar.bz2
860f9099c7c11b259562c762e03a8a11f4da1a5cea43e44fc138669419cb9468 35524 postgresql-10_10.16-0ubuntu0.18.04.1.debian.tar.xz
1c66abb68867e6225c58896b7c46c5cb35fdafd8615ad59eb5f1e6ffba058346 8238 postgresql-10_10.16-0ubuntu0.18.04.1_source.buildinfo
Files:
1437414d7280c715ccf77b2fe105d940 3620 database optional postgresql-10_10.16-0ubuntu0.18.04.1.dsc
7481231d870d416b3ad7ba0edeadc021 19140221 database optional postgresql-10_10.16.orig.tar.bz2
b894ddad67ea2865cb3b2f510a8b9e76 35524 database optional postgresql-10_10.16-0ubuntu0.18.04.1.debian.tar.xz
4a3088336f5752c9894ebfbcfb26c6e2 8238 database optional postgresql-10_10.16-0ubuntu0.18.04.1_source.buildinfo
Original-Maintainer: Debian PostgreSQL Maintainers <pkg-postgresql-public at lists.alioth.debian.org>
More information about the Bionic-changes
mailing list