Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors
Date
Msg-id alpine.DEB.2.22.394.2204041518020.3174331@pseudo
Whole thread Raw
In response to Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors  (Tatsuo Ishii <ishii@sraoss.co.jp>)
Responses Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors
List pgsql-hackers
Hello Tatsuo-san,

> interval_start num_transactions sum_latency sum_latency_2 min_latency max_latency
> sum_lag sum_lag_2 min_lag max_lag skipped
> failures serialization_failures deadlock_failures retried retries

I would suggest to reorder the last chunk to:

    ... retried retries failures serfail dlfail

because I intend to add connection failures handling at some point, and it 
would make more sense to add the corresponding count at the end with other 
fails.

-- 
Fabien Coelho - CRI, MINES ParisTech



pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: Handle infinite recursion in logical replication setup
Next
From: Jesper Pedersen
Date:
Subject: Re: GSoC: pgmoneta, storage API