On Thu, Nov 12, 2009 at 11:55:48AM -0500, Brad Nicholson wrote:

> We've seen this problem before with 8.1.  While it is exceedingly hard
> to trace exactly what is going on, all signs pointed to a bug in
> Postgres.  We couldn't reproduce it though.
> 
> If I were you, I would upgrade to the latest minor version of your PG
> release - you are 16 minor version behind.  They fix it for a reason :-)

What Brad said.  Also, note that the symptoms could be the result of
corrupt indexes.  If reindexing the databases at both ends makes this
problem magically disappear, you need to investigate what's happening
at the underlying hardware.  (I've seen this problem, too.)

A

-- 
Andrew Sullivan
ajs at crankycanuck.ca