From: r.zharkov@postgrespro.ru
To: Andres Freund <andres@anarazel.de>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed
Date: Sun, 07 Apr 2019 00:09:15 +0700
Message-ID: <199712fc251b6216f106edd07770d6c4@postgrespro.ru> (raw)
In-Reply-To: <20190406162846.uohf5lcybz4ldrxh@alap3.anarazel.de>
References: <20190403122027.GA17929@alvherre.pgsql>
<994bff111c549f45041cd1dc7473548e@postgrespro.ru>
<19321.1554567786@sss.pgh.pa.us>
<20190406162846.uohf5lcybz4ldrxh@alap3.anarazel.de>
On 2019-04-06 23:28, Andres Freund wrote:
> Hi,
>
> Let me have a look at the testcase - I'd been running Roman's testcase
> for quite a few hours without being able to reproduce. But your
> testcase
> seems to trigger this reliably, so I hope I can make some quick
> progress.
>
> - Andres
Hello,
I try to find the bad commit using bisect. But it takes very long time.
The error reproduces with the default config using 24 clients ( server
has 24 CPUs )
pgbench test -j 12 -T 36000 -f ycsb_read_zipf.sql -f
ycsb_update_zipf.sql -c 24 -P 60
It does not reproduce when updating the only one record.
CPU configuration:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 24
On-line CPU(s) list: 0-23
Thread(s) per core: 2
Core(s) per socket: 6
Socket(s): 2
NUMA node(s): 2
Vendor ID: GenuineIntel
CPU family: 6
Model: 44
Model name: Intel(R) Xeon(R) CPU X5675 @ 3.07GHz
Stepping: 2
CPU MHz: 2464.940
CPU max MHz: 3066.0000
CPU min MHz: 1600.0000
BogoMIPS: 6133.57
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 12288K
NUMA node0 CPU(s): 0,2,4,6,8,10,12,14,16,18,20,22
NUMA node1 CPU(s): 1,3,5,7,9,11,13,15,17,19,21,23
--
regards,
Roman Zharkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: r.zharkov@postgrespro.ru, andres@anarazel.de, tgl@sss.pgh.pa.us, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed
In-Reply-To: <199712fc251b6216f106edd07770d6c4@postgrespro.ru>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox