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

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