This bug was fixed in the package postgresql-8.3 - 8.3.22-0ubuntu8.04 --------------- postgresql-8.3 (8.3.22-0ubuntu8.04) hardy-proposed; urgency=low
* New upstream bug fix release: (LP: #1088393) - Fix multiple bugs associated with "CREATE INDEX CONCURRENTLY". Fix "CREATE INDEX CONCURRENTLY" to use in-place updates when changing the state of an index's pg_index row. This prevents race conditions that could cause concurrent sessions to miss updating the target index, thus resulting in corrupt concurrently-created indexes. Also, fix various other operations to ensure that they ignore invalid indexes resulting from a failed "CREATE INDEX CONCURRENTLY" command. The most important of these is "VACUUM", because an auto-vacuum could easily be launched on the table before corrective action can be taken to fix or remove the invalid index. - See HISTORY/changelog.gz for details about the other bug fixes. -- Martin Pitt <martin.p...@ubuntu.com> Mon, 10 Dec 2012 16:16:57 +0100 ** Changed in: postgresql-8.3 (Ubuntu Hardy) Status: Fix Committed => Fix Released ** Changed in: postgresql-8.4 (Ubuntu Lucid) 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/1088393 Title: New bug fix releases: 9.1.7, 8.4.15, 8.3.22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-8.3/+bug/1088393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs