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

From Andres Freund
Subject Re: BUG #15727: PANIC: cannot abort transaction 295144144, it wasalready committed
Date
Msg-id 20190402171152.lmdbcnlhyakexujl@alap3.anarazel.de
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)
List pgsql-bugs
Hi,

On 2019-04-03 00:04:15 +0700, r.zharkov@postgrespro.ru wrote:
> pgbench connects to the database through the connection pooller called
> Odyssey.
> We use pool of 16 or 32 backends.
> We run four series of pgbench tests with different connections count ( 100,
> 150, 200, ... , 1000 )
> Three series with pool size 16 runs normally.
> But fourth series fails with 200-300 connections. It took about five hours
> to reproduce the error this time.
> 
> Here is the little piece of the pgbench log:
> 
> Bench start
> Tue Apr  2 14:43:12 UTC 2019
> Timestamp 1554216192
> transaction type: multiple scripts
> scaling factor: 1

Is this the actual scaling factor? Did you create the pgbench database
with foreign keys?

Greetings,

Andres Freund



pgsql-bugs by date:

Previous
From: Jeff Janes
Date:
Subject: Re: BUG #15722: 9000x performance regression on query startingPostgreSQL 10 due to bad query plan
Next
From: Tom Lane
Date:
Subject: Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed