| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>, 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-03 11:54:14 |
| Message-ID: | 202204031154.qrl4cvuumzcl@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2022-04-03 12:59:54 | Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors |
| Previous Message | Tatsuo Ishii | 2022-04-03 11:44:36 | Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors |