From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Barry Lind <barry(at)xythos(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Core dump on 7.1.3 on Linux 2.2.19 |
Date: | 2001-11-06 01:31:40 |
Message-ID: | 4510.1005010300@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Barry Lind <barry(at)xythos(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Barry Lind | 2001-11-06 01:41:33 | Core dump on 7.1.3 on Linux 2.2.19 |
Previous Message | Liam Stewart | 2001-11-05 23:26:28 | Re: Funny timezone shift causes failure in test suite |