diff options
| author | Fujii Masao | 2021-01-13 13:59:17 +0000 |
|---|---|---|
| committer | Fujii Masao | 2021-01-13 13:59:17 +0000 |
| commit | 39b03690b529935a3c33024ee68f08e2d347cf4f (patch) | |
| tree | 535e89716c5be4aebec5debb1db1e37e6f0d43c3 /src/include | |
| parent | 6ecaaf810b8b9e3132f00549e630400f38a7ca37 (diff) | |
Log long wait time on recovery conflict when it's resolved.
This is a follow-up of the work done in commit 0650ff2303. This commit
extends log_recovery_conflict_waits so that a log message is produced
also when recovery conflict has already been resolved after deadlock_timeout
passes, i.e., when the startup process finishes waiting for recovery
conflict after deadlock_timeout. This is useful in investigating how long
recovery conflicts prevented the recovery from applying WAL.
Author: Fujii Masao
Reviewed-by: Kyotaro Horiguchi, Bertrand Drouvot
Discussion: https://postgr.es/m/[email protected]
Diffstat (limited to 'src/include')
| -rw-r--r-- | src/include/storage/standby.h | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/src/include/storage/standby.h b/src/include/storage/standby.h index a0f3e0bdf09..2b1f340b82b 100644 --- a/src/include/storage/standby.h +++ b/src/include/storage/standby.h @@ -40,7 +40,8 @@ extern void StandbyDeadLockHandler(void); extern void StandbyTimeoutHandler(void); extern void StandbyLockTimeoutHandler(void); extern void LogRecoveryConflict(ProcSignalReason reason, TimestampTz wait_start, - TimestampTz cur_ts, VirtualTransactionId *wait_list); + TimestampTz cur_ts, VirtualTransactionId *wait_list, + bool still_waiting); /* * Standby Rmgr (RM_STANDBY_ID) |