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

From Tatsuo Ishii
Subject Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors
Date
Msg-id 20220403.204436.1773286534982306996.t-ishii@sranhm.sra.co.jp
Whole thread Raw
In response to Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors  (Fabien COELHO <coelho@cri.ensmp.fr>)
List pgsql-hackers
>>> Or those three columns always, sum_lag sum_lag_2, min_lag max_lag,
>>> skipped, retried retries?
>>
>> 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 ] ] ?
>
> Alterlatively, as the failure stuff is added to the format, maybe it
> could be at the end:
>
>   [ sum_lag ... [ skipped [ fails ... retries ] ] ] ?

I like this one.

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 ] ] ]

Best reagards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Higher level questions around shared memory stats
Next
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors