Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors
От | Fabien COELHO |
---|---|
Тема | Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors |
Дата | |
Msg-id | alpine.DEB.2.22.394.2204030956500.2117840@pseudo обсуждение исходный текст |
Ответ на | Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors (Tatsuo Ishii <ishii@sraoss.co.jp>) |
Ответы |
Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors
Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors |
Список | 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 ] ] ] ? > failures: > always 0 (if --max-tries is 1, the default) > sum of serialization_failures and deadlock_failures (if --max-tries is not 1) > > serialization_failures and deadlock_failures: > always 0 (if --max-tries is 1, the default) > 0 or more (if --max-tries is not 1) > > retried and retries: > always 0 (if --max-tries is 1, the default) > 0 or more (if --max-tries is not 1) > > Best reagards, > -- > Tatsuo Ishii > SRA OSS, Inc. Japan > English: http://www.sraoss.co.jp/index_en.php > Japanese:http://www.sraoss.co.jp > -- Fabien.
В списке pgsql-hackers по дате отправления: