Barry Lind <barry@xythos.com> writes:
> It happened to me this afternoon while running a 'vacuum analyze
> verbose'. I have attached the stack trace below.
That trace is certainly not from a vacuum operation.
I'd suggest rebuilding with --enable-debug; we won't be able to learn
much without that. Until you do that, possibly it'd help to turn on
query logging so that we can learn what query is crashing.
I find the presence of EvalPlanQual in the backtrace suggestive.
I don't trust that code at all ;-) ... but without a lot more info
we're not going to be able to figure out anything.
BTW, EvalPlanQual is only called if the query is an UPDATE or DELETE
that tries to update a row that's already been updated by a
not-yet-committed transaction. That probably explains why you don't
see the crash often --- if you deliberately set up the right
circumstances, you could perhaps reproduce it on-demand.
regards, tom lane