Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed

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
Date: 2019-04-08 08:18:48
Message-ID: 223f3fa6-3075-47fd-3caa-0d5e8dee1baa@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2019/04/08 16:21, Amit Langote wrote:
> Now that Andres has taken care of the other issues [1], 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.

The patch I attached in the previous email doesn't apply as-is to
back-branches due to rebasing. I've attached another patch here, which
applies to both PG 11 and 10 branches.

Thanks,
Amit

Attachment Content-Type Size
pg11-10-bug-15677-fix-with-test_v2.patch text/plain 3.9 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Kadam, Daulat (BHGE, consultant) 2019-04-08 10:23:37 PostgreSQL 9.5 service stopped intermittently on windows 10 Pro version 1703.
Previous Message Michael Paquier 2019-04-08 07:39:03 Re: BUG #15734: Walsender process crashing when executing SHOW ALL;