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
This bug was fixed in the package postgresql-8.4 - 8.4.15-0ubuntu12.04
---
postgresql-8.4 (8.4.15-0ubuntu12.04) precise-proposed; urgency=low
* New upstream bug fix release: (LP: #1088393)
- Fix multiple bugs associated with CREATE INDEX CONCURRENTLY
Fix CREATE INDEX
This bug was fixed in the package postgresql-9.1 - 9.1.7-0ubuntu11.10
---
postgresql-9.1 (9.1.7-0ubuntu11.10) oneiric-proposed; urgency=low
* New upstream bug fix release: (LP: #1088393)
- Fix multiple bugs associated with CREATE INDEX CONCURRENTLY.
Fix CREATE INDEX
This bug was fixed in the package postgresql-9.1 - 9.1.7-0ubuntu12.10
---
postgresql-9.1 (9.1.7-0ubuntu12.10) quantal-proposed; urgency=low
* New upstream bug fix release: (LP: #1088393)
- Fix multiple bugs associated with CREATE INDEX CONCURRENTLY.
Fix CREATE INDEX
This bug was fixed in the package postgresql-9.1 - 9.1.7-0ubuntu12.04
---
postgresql-9.1 (9.1.7-0ubuntu12.04) precise-proposed; urgency=low
* New upstream bug fix release: (LP: #1088393)
- Fix multiple bugs associated with CREATE INDEX CONCURRENTLY.
Fix CREATE INDEX
This bug was fixed in the package postgresql-8.4 - 8.4.15-0ubuntu10.04
---
postgresql-8.4 (8.4.15-0ubuntu10.04) lucid-proposed; urgency=low
* New upstream bug fix release: (LP: #1088393)
- Fix multiple bugs associated with CREATE INDEX CONCURRENTLY
Fix CREATE INDEX
With hardy's glibc regression now being fixed in -security/-updates, the
new postgresql update built fine on i386 and lpia. I ran the p-common
regression tests successfully.
** Changed in: postgresql-8.3 (Ubuntu Hardy)
Status: In Progress = Fix Committed
** Tags removed:
I've located the glibc regression and will publish an update for it on
monday.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-9.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1088393
Title:
New bug fix releases: 9.1.7,
(glibc issue tracked in bug #1090740)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-9.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1088393
Title:
New bug fix releases: 9.1.7, 8.4.15, 8.3.22
Status in “postgresql-8.3”
I'm chasing the test case failure on i386/lpia which caused a build
failure:
***
*** 432,443
select * from numeric_table
where num_col in (select float_col from float_table);
num_col
! -
1
-
precise 8.4 and 9.1 and lucid 8.4 -proposed versions verified with
postgresql-common test suite.
** Tags added: verification-done-precise verification-failed-hardy
** Changed in: postgresql-9.1 (Ubuntu Precise)
Status: In Progress = Fix Committed
** Changed in: postgresql-8.4 (Ubuntu
** Tags added: verification-done-oneiric verification-done-quantal
** Tags removed: verification-needed
** Changed in: postgresql-9.1 (Ubuntu Oneiric)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is
I bisected the hardy failure on i386 and lpia down to this glibc
upgrade:
https://launchpad.net/ubuntu/+source/glibc/2.7-10ubuntu8.2
Both postgresql 8.3.21 and 8.3.22 build fine on hardy final, and fail
the same way as in comment 9 on a fully upgraded hardy. Downgrading
libc6, libc6-dev, and
** Branch unlinked: lp:ubuntu/precise-proposed/postgresql-8.4
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-9.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1088393
Title:
New bug fix releases: 9.1.7, 8.4.15, 8.3.22
Status
Hello Martin, or anyone else affected,
Accepted into quantal-proposed. The package will build now and be
available in a few hours in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use
** Branch linked: lp:ubuntu/lucid-proposed/postgresql-8.4
** Branch linked: lp:ubuntu/precise-proposed/postgresql-8.4
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-9.1 in Ubuntu.
https://bugs.launchpad.net/bugs/1088393
Synced 9.1.7-1 from Debian unstable into Raring.
** Changed in: postgresql-9.1 (Ubuntu Raring)
Status: New = Fix Released
** No longer affects: postgresql-8.4 (Ubuntu Hardy)
** No longer affects: postgresql-8.4 (Ubuntu Raring)
** No longer affects: postgresql-8.4 (Ubuntu Quantal)
** No
I uploaded the 9.1 updates to the -proposed SRU review queues.
** Changed in: postgresql-9.1 (Ubuntu Oneiric)
Status: New = In Progress
** Changed in: postgresql-9.1 (Ubuntu Precise)
Status: New = In Progress
** Changed in: postgresql-9.1 (Ubuntu Quantal)
Status: New = In
I uploaded the two 8.4 updates (lucid/precise) to the SRU review queue.
** Changed in: postgresql-8.4 (Ubuntu Lucid)
Status: New = In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-9.1 in Ubuntu.
8.3/hardy update uploaded to SRU review queue, too.
** Changed in: postgresql-8.4 (Ubuntu Precise)
Status: New = In Progress
** Changed in: postgresql-8.3 (Ubuntu Hardy)
Status: New = In Progress
--
You received this bug notification because you are a member of Desktop
Packages,
20 matches
Mail list logo
