"Ashley @ Turton" ashley@turton.com writes:

not changed any settings for a long time and it only started playing up today. Any ideas?

Not really. We've not seen this, but I think we only have Postgres 6.5.3 and 7.1 here. tsw uses a 7.0 version, but that hasn't had any problems either.

Have you checked for open bug reports at postgresql.org and on their lists?