| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | r(dot)zharkov(at)postgrespro(dot)ru |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed |
| Date: | 2019-04-02 17:11:52 |
| Message-ID: | 20190402171152.lmdbcnlhyakexujl@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi,
On 2019-04-03 00:04:15 +0700, r(dot)zharkov(at)postgrespro(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-04-02 17:13:58 | Re: BUG #15727: PANIC: cannot abort transaction 295144144, it was already committed |
| Previous Message | Jeff Janes | 2019-04-02 17:10:48 | Re: BUG #15722: 9000x performance regression on query starting PostgreSQL 10 due to bad query plan |