Reduce log verbosity during prepared transaction recovery Previously, RecoverPreparedTransactions() logged each prepared transaction at LOG level at the end of recovery. With many unresolved prepared transactions, these messages could clutter the server log.
Lower the severity of these messages to DEBUG2, matching the messages in PrepareRedoAdd() and PrepareRedoRemoveFull(), and report the number of successfully recovered prepared transactions in a single LOG message. This reduces log clutter while retaining per-transaction details at DEBUG2. Author: Ashutosh Sharma <[email protected]> Reviewed-by: Jakub Wartak <[email protected]> Reviewed-by: Pierre Forstmann <[email protected]> Reviewed-by: Chao Li <[email protected]> Reviewed-by: Fujii Masao <[email protected]> Discussion: https://postgr.es/m/cae9k0pmq1qqevtkqsbtwuawrnw+191zctbpvkmmp5e3x2c+...@mail.gmail.com Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/c11eb5de01ba3401e880195888fb25703e0edf10 Modified Files -------------- src/backend/access/transam/twophase.c | 16 ++++++++++++---- src/test/recovery/t/009_twophase.pl | 15 +++++++++++++-- 2 files changed, 25 insertions(+), 6 deletions(-)
