Vince Clark wrote:
This is a really strange problem that has me stumped. It only occurs on servers I have in a data center that are virtualized. The problem does not occur locally on my SuSE 10.1 laptop, postgres 8.1.4.
<snip>
Postgres 8.0.2
I've been reading up until the last few weeks every mail on the postgresql-general mailing list for nearly 6 months, and I can't recall anyone who would recommend any 8.0 version. From reading peoples random ills I would consider 8.0 versions Beta.
From following many peoples success stories on the list, you should be fine with the 8.1 version, but be aware that 8.2 version runs significantly faster, as will 8.3 even more.
The developers seem to state that if you are on 8.1 then it will be worth the pain (dump/restore) to move to 8.3 when it becomes available.
The only old version that seems to be worthwhile is a 7.4 branch that RedHat is paying a developer to backport fixes on a full time basis.
So, Can you not get a more modern version of postgreSQL?
