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
Дата
Msg-id c4387afc59627736ed6c57617243d0bb@postgrespro.ru
обсуждение исходный текст
Ответ на Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed  (Thomas Munro <thomas.munro@gmail.com>)
Ответы Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed  (Thomas Munro <thomas.munro@gmail.com>)
Список pgsql-bugs
Дерево обсуждения 
On 2019-04-11 15:52, Thomas Munro wrote:
> 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.

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

-- 
regards,
Roman Zharkov

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: Suspicious strcmp() in src/backend/parser/parse_expr.c
Следующее
От: r.zharkov@postgrespro.ru
Дата:
Сообщение: Re: BUG #15746: cache lookup failed for function in plpgsql block