|From:||Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>|
|To:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, r(dot)zharkov(at)postgrespro(dot)ru|
|Cc:||Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, 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/07 1:23, Tom Lane wrote:
> It seems that there may be some connection between this problem and
> EPQ. I was working on committing Amit's fix for bug #15677, which
> demonstrated that EPQ doesn't work for partitioned-table target rels.
> It seemed like there really needed to be regression test coverage for
> that, so I tried to convert his crasher example into an isolation test.
> It does indeed crash without Amit's fix ... but with it, lookee what
> I get:
> +error in steps c1 complexpartupdate: ERROR: unexpected table_lock_tuple status: 1
> That seems fully reproducible in this test. I haven't looked into
> exactly what's causing that, but now that we have a reproducible
> example, somebody should.
> I'm not quite sure if I should commit this as-is or wait till the
> other problem is fixed. A crash is probably worse than a bogus
> error, but I don't like committing obviously-wrong "expected" output.
Thank you Tom for picking it up and adding the test which I should've done
to begin with.
Now that Andres has taken care of the other issues , maybe this one's
good to go? The isolation test part needed to be rebased over Andres'
commit, which I've done in the attached updated patch.
|Next Message||Michael Paquier||2019-04-08 07:39:03||Re: BUG #15734: Walsender process crashing when executing SHOW ALL;|
|Previous Message||Amit Langote||2019-04-08 04:55:13||Re: BUG #15733: An insert destined at partition created after a column has been dropped from the parent table fails|