Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed - Mailing list pgsql-bugs

From Thomas Munro
Subject Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed
Date
Msg-id CA+hUKGL_PQ4WeC1uh7=ABkr0comOYTBjzjYsDUrPT11Kk6WHaQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed  (r.zharkov@postgrespro.ru)
Responses Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed  (r.zharkov@postgrespro.ru)
Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed  (r.zharkov@postgrespro.ru)
List pgsql-bugs
On Thu, Apr 11, 2019 at 5:35 PM <r.zharkov@postgrespro.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.

-- 
Thomas Munro
https://enterprisedb.com

Attachment

pgsql-bugs by date:

Previous
From: Amit Langote
Date:
Subject: Re: BUG #15672: PostgreSQL 11.1/11.2 crashed after dropping apartition table
Next
From: PG Bug reporting form
Date:
Subject: BUG #15747: Help says 'application_name' property supports 64 characters in a standard built but it's only 63