Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>
Cc: alvherre(at)alvh(dot)no-ip(dot)org, tgl(at)sss(dot)pgh(dot)pa(dot)us, nagata(at)sraoss(dot)co(dot)jp, thomas(dot)munro(at)gmail(dot)com, m(dot)polyakova(at)postgrespro(dot)ru, pgsql-hackers(at)postgresql(dot)org, teodor(at)sigaev(dot)ru
Subject: Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors
Date: 2022-04-04 13:20:43
Message-ID: alpine.DEB.2.22.394.2204041518020.3174331@pseudo
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jesper Pedersen 2022-04-04 13:23:58 Re: GSoC: pgmoneta, storage API
Previous Message Ashutosh Bapat 2022-04-04 13:20:08 Re: Handle infinite recursion in logical replication setup