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-11 05:35:34
Message-ID: 4f774e94b0ec4942a265947efb493b35@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2019-04-11 11:44, Thomas Munro wrote:
>> Cool, thanks for confirming.
>
> Thanks. Looking into this.

Hi,
I think that the problem is in the autovacuum.

...
2019-04-11 08:04:49.593 MSK [24671] LOG: automatic analyze of table
"test.public.pgbench_accounts" system usage: CPU: user: 0.15 s, system:
0.00 s, elapsed: 0.17 s
2019-04-11 08:05:29.137 MSK [13263] LOG: checkpoint starting: wal
2019-04-11 08:05:49.352 MSK [25040] LOG: automatic analyze of table
"test.public.pgbench_accounts" system usage: CPU: user: 0.15 s, system:
0.00 s, elapsed: 0.18 s
2019-04-11 08:06:49.449 MSK [25058] LOG: automatic vacuum of table
"test.public.pgbench_accounts": index scans: 1
pages: 0 removed, 2145 remain, 1 skipped due to pins, 0 skipped
frozen
tuples: 8349 removed, 100975 remain, 976 are dead but not yet
removable, oldest xmin: 195581926
buffer usage: 6303 hits, 0 misses, 43 dirtied
avg read rate: 0.000 MB/s, avg write rate: 1.353 MB/s
system usage: CPU: user: 0.16 s, system: 0.00 s, elapsed: 0.24 s
2019-04-11 08:06:49.623 MSK [25058] LOG: automatic analyze of table
"test.public.pgbench_accounts" system usage: CPU: user: 0.13 s, system:
0.01 s, elapsed: 0.17 s
2019-04-11 08:06:57.478 MSK [13263] LOG: checkpoint complete: wrote
2378 buffers (14.5%); 0 WAL file(s) added, 0 removed, 42 recycled;
write=88.322 s, sync=0.000 s, total=88.340 s; sync fi
les=6, longest=0.000 s, average=0.000 s; distance=688127 kB,
estimate=688128 kB
2019-04-11 08:07:49.451 MSK [25084] LOG: automatic analyze of table
"test.public.pgbench_accounts" system usage: CPU: user: 0.15 s, system:
0.01 s, elapsed: 0.22 s
2019-04-11 08:08:28.963 MSK [13263] LOG: checkpoint starting: wal
2019-04-11 08:08:49.500 MSK [25100] LOG: automatic vacuum of table
"test.public.pgbench_accounts": index scans: 1
pages: 0 removed, 2145 remain, 1 skipped due to pins, 0 skipped
frozen
tuples: 8666 removed, 101047 remain, 1047 are dead but not yet
removable, oldest xmin: 198748530
buffer usage: 6243 hits, 0 misses, 15 dirtied
avg read rate: 0.000 MB/s, avg write rate: 0.480 MB/s
system usage: CPU: user: 0.17 s, system: 0.00 s, elapsed: 0.24 s
2019-04-11 08:08:49.678 MSK [25100] LOG: automatic analyze of table
"test.public.pgbench_accounts" system usage: CPU: user: 0.13 s, system:
0.01 s, elapsed: 0.17 s
TRAP: FailedAssertion("!((((tuple->t_data->t_infomask) & 0x0080) ||
(((tuple->t_data->t_infomask) & (0x1000 | ((0x0040 | 0x0010) | 0x0040 |
0x0010))) == 0x0040)))", File: "heapam.c", Line:
4289)
2019-04-11 08:09:37.452 MSK [13261] LOG: server process (PID 13294) was
terminated by signal 6: Aborted
2019-04-11 08:09:37.452 MSK [13261] DETAIL: Failed process was running:
UPDATE pgbench_accounts SET abalance = 1 WHERE aid = 2;

--
regards,

Roman Zharkov

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2019-04-11 06:50:55 Re: Suspicious strcmp() in src/backend/parser/parse_expr.c
Previous Message Pavel Stehule 2019-04-11 05:00:46 Re: BUG #15709: if drop exists syntax