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

From Alvaro Herrera
Subject Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors
Date
Msg-id 202204031154.qrl4cvuumzcl@alvherre.pgsql
Whole thread Raw
In response to Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors  (Fabien COELHO <coelho@cri.ensmp.fr>)
Responses Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors  (Tatsuo Ishii <ishii@sraoss.co.jp>)
Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2022-Apr-03, Fabien COELHO wrote:

> > What about this? (a log line is not actually folded)
> > interval_start num_transactions sum_latency sum_latency_2 min_latency max_latency
> > failures serialization_failures deadlock_failures retried retries [ sum_lag sum_lag_2 min_lag max_lag [ skipped ]
]
> 
> My 0.02€:
> 
> I agree that it would be better to have a more deterministic aggregated log
> format.
> 
> ISTM that it should skip failures and lags if no fancy options has been
> selected, i.e.:
> 
>   [ fails ... retries [ sum_lag ... [ skipped ] ] ?

I think it's easier to just say "if feature X is not enabled, then
columns XYZ are always zeroes".

-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/



pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors
Next
From: Tatsuo Ishii
Date:
Subject: Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors