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

From: Жарков Роман <r(dot)zharkov(at)postgrespro(dot)ru>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed
Date: 2019-04-11 04:17:54
Message-ID: ACFBFD01-D22B-429D-946E-9F1CD68F2616@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> 11 апр. 2019 г., в 10:47, Michael Paquier <michael(at)paquier(dot)xyz> написал(а):
>
>> On Thu, Apr 11, 2019 at 10:29:03AM +0700, r(dot)zharkov(at)postgrespro(dot)ru wrote:
>> The error does not reproduce on commit 2fc7af5 on both servers.
>
> Okay. As nothing seems to remain here, I have marked this open item
> as fixed.
> --
> Michael

Hi,
There is no fix. 2fc7af5 is the last good commit.

regards,
Roman

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2019-04-11 04:23:42 Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed
Previous Message Jueve L 2019-04-11 04:17:11 Re: BUG #15709: if drop exists syntax