Vivek Khera <khera@kcilink.com> writes:
> Curiously, last time I did this (July 4), I got the same error, so I
> really doubt it is an open transaction, unless such a thing survives
> db shutdown and restart ;-)
Yes, there is one known variant that survives a shutdown. I am certain
that that form of the problem is patched in 7.2.3-RH (Red Hat's
release), but don't recall if it's in the community 7.2.3 release or
not. In any case the fix is in 7.3, along with fixes for other cases
that can produce the same error message.
regards, tom lane
