|From:||Andres Freund <andres(at)anarazel(dot)de>|
|To:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|Cc:||r(dot)zharkov(at)postgrespro(dot)ru, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org|
|Subject:||Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On 2019-04-02 13:30:56 -0400, Tom Lane wrote:
> But it's hardly plausible that that runs post-commit.
Yea, one surely would hope that that's not happening. I suspect it's
possible it's running pre-commit and somehow the failure handling is
screwed up leading to the 'already committed' error.
> So now I'm thinking that what we really need to know is why a
> TM_Invisible result was returned. That's going to be a bit harder ...
Yea. I re-skimmed through the code and can't immediately see anything
wrong - not that such subtle issues would necessarily be noticed without
I wonder, is there a chance that you're using an extension with xact
hooks, or a modified version of postgres? Could you show us the exact
schema used, and the config?
|Next Message||Thomas Munro||2019-04-02 19:54:34||Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker|
|Previous Message||Жарков Роман||2019-04-02 17:35:47||Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed|