From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Oliver Elphick" <olly(at)lfix(dot)co(dot)uk> |
Cc: | "G(dot) Anthony Reina" <reina(at)nsi(dot)edu>, "pgsql-hackers(at)postgreSQL(dot)org" <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] Aborted Transaction During Vacuum |
Date: | 1999-08-13 21:31:47 |
Message-ID: | 6178.934579907@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Oliver Elphick" <olly(at)lfix(dot)co(dot)uk> writes:
>> But the vc_abort problem didn't cause a backend coredump --- it just
>> reported an error and failed to complete the vacuum, no?
> I got a coredump too; I never mentioned it, because I found the proximate
> cause and curing that made it go away. When unlink failed in vc_shutdown,
> it called ELOG and a segfault occurred a little later.
Ah, I wish I'd known that. So what Tony is seeing is exactly the same
behavior you observed. OK, I feel better now --- I thought the coredump
was probably some platform-specific misbehavior that only Tony was seeing.
We still need to figure out what is causing it, because I can see no
reason for a coredump after vc_shutdown elog()s. Something is being
clobbered that should not be. But it sounds like installing the
vc_abort patch will get Tony on his feet, and then we can look for the
secondary bug at our leisure.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 1999-08-13 22:17:53 | Ah-hah, I see the problem: EndPortalAllocMode() |
Previous Message | Tom Lane | 1999-08-13 21:22:37 | Re: [HACKERS] Aborted Transaction During Vacuum |