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

From: r(dot)zharkov(at)postgrespro(dot)ru
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed
Date: 2019-04-12 02:44:04
Message-ID: c4387afc59627736ed6c57617243d0bb@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2019-04-11 15:52, Thomas Munro wrote:
> On Thu, Apr 11, 2019 at 5:35 PM <r(dot)zharkov(at)postgrespro(dot)ru> wrote:
>> TRAP: FailedAssertion("!((((tuple->t_data->t_infomask) & 0x0080) ||
>> (((tuple->t_data->t_infomask) & (0x1000 | ((0x0040 | 0x0010) | 0x0040
>> |
>> 0x0010))) == 0x0040)))", File: "heapam.c", Line:
>> 4289)
>
> Hi Roman,
>
> Ah, I see it. Can you reproduce the problem with this patch applied?
>
> While going over that commit spotted an incorrect sizeof in
> EstimateTransactionStateSpace(), but I'll fix that separately.

Hello,
My test finished successfully. Everything is OK.
Thanks!

--
regards,
Roman Zharkov

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message r.zharkov 2019-04-12 03:22:09 Re: BUG #15746: cache lookup failed for function in plpgsql block
Previous Message Michael Paquier 2019-04-12 01:29:54 Re: Suspicious strcmp() in src/backend/parser/parse_expr.c