New minor version available with some fixes. One fix prevents rows to be lost under certain conditons: "Fix whole-index GiST scans to work correctly (Teodor) This error could cause rows to be lost if a table is clustered on a GiST index." Emerging the new version works with renamed ebuilds. The resulting postgresql works so far in my development environment. Reproducible: Always Steps to Reproduce:
Works here too. please add to ~testing
Please add to ~arch. :)
I'm eager for this version bump too: ubuntu 8.10 intrepid is on postgresql-8.3.6 as of yesterday, and the pg_dump plaintext ordering of schema elements has changed, resulting in unwanted diff artifacts between 8.3.5 and 8.3.6.
(In reply to comment #3) > I'm eager for this version bump too: ubuntu 8.10 intrepid is on > postgresql-8.3.6 as of yesterday, and the pg_dump plaintext ordering of schema > elements has changed, resulting in unwanted diff artifacts between 8.3.5 and > 8.3.6. > This is due to a bug in the order of composite types. See [1] for details. Also, PostgreSQL doesn't guarantee pg_dump order. [1] http://www.postgresql.org/docs/8.3/static/release-8-3-6.html
8.3.7 is out any second now. Skip 8.3.6 entirely perhaps?
(In reply to comment #5) > 8.3.7 is out any second now. Skip 8.3.6 entirely perhaps? I bumped my ebuilds already and it just works, so yes. Maybe we can also kick off a stabilization request, as 8.4 is just around the corner. Current stable is the ancient pre-slotted 8.0 version :(
*** Bug 262860 has been marked as a duplicate of this bug. ***
(In reply to comment #6) > (In reply to comment #5) > > 8.3.7 is out any second now. Skip 8.3.6 entirely perhaps? > > I bumped my ebuilds already and it just works, so yes. Maybe we can also kick > off a stabilization request, as 8.4 is just around the corner. Current stable > is the ancient pre-slotted 8.0 version :( I agree. The 8.3 branch is treated as stable on many larger companies and brought enough features to motivate a move from < 8.3. The only version one perhaps should avoid is 8.3.4 and its GIN index bug
bug 230817 is the stabilization request, and yes all the new versions are out so you might as well skip the ones you missed.
,-docs should be in the summary
8.3.7 is in portage. Is anyone interested really in the other versions?
(In reply to comment #11) > 8.3.7 is in portage. Is anyone interested really in the other versions? > I'd advise against anything except the latest minor which basically is what postgresql recommends in their "upgrade guide" as well. I guess PostGreSQL 8.4 beta could be interesting to start testing out?
Been there, done that. Didn't get a T-Shirt.
