PostgreSQL 9.0 Released

poet writes "Today the PostgreSQL Global Development Group released PostgreSQL 9.0. This release marks a major milestone in the PostgreSQL ecosystem, with added features such as streaming replication (including DDL), Hot Standby and other nifty items like DO. The release notes list all the new features, and the guide explains them in greater detail. You can download a copy now."

Comments

Re:Waiting for a capable PostgreSQL front-end

[abigor]

Probably OpenOffice Base is your best bet. I've never tried it, but I know it's often put forward as an Access alternative. But like most things OpenOffice, it probably falls short in several (or many) respects.

Re:Cool

[Mike D. Kristopeit]

YOU are the reason why so many projects require complete rewrites when a single feature is added or removed or altered.

relying on regression testing as a tool of the development process rather than a tool of the final product testing, and thus relying on the regression tests themselves to dictate when code is deliverable instead of relying on developers who have ensured regressions CAN NOT EXIST can NEVER be the right decision.

keep pushing the idea that developers are idiots... why could you possibly benefit from pushing such an idea? perhaps you are an idiot developer, or an idiot that knows they are incapable of developing.

Re:Cool

[Kristopeit,MichaelDa]

coward.

you are NOTHING

Re:Has the Documentation Been Improved?

[GoChickenFat]

I get rated a Troll and the original parent also because we don't love the PG documentation? What gives? Clearly the troll in this equation is the idiot with the mod points.
TAKE IT

Re:Cool

[Enleth]

An idiot prepared the server hardware requirements, then. A simple PCI-E card with a few RAM slots, a LiIon battery pack and a faux SATA controller (they are available from a few vendors and cost a few hundred bucks a piece, pretty cheap for such a thing), configured as the WAL store - the database had a write-ahead log, right? - would increase the capacity of a single such server at least tenfold.

The problem wasn't that the databse was used in a wrong way. Rather, it was a lack of a systems integration person in the team, who grasps all the general aspects of the deployment from the frontend down to the bare metal and can identify such problems and find remedies right when they occur.