Re: Reduce logging during prepared transaction recovery

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>
Cc: Pierre Forstmann <pierre(dot)forstmann(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Reduce logging during prepared transaction recovery
Date: 2026-10-29 14:11:15
Message-ID: CAHGQGwE4rrUdCaxye3q1jf_3wjpyxhs7j_5_Gw+Kz_oFzLdycA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 29, 2026 at 2:30 PM Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com> wrote:
> It's a developer-facing message, so I agree that it doesn't need to be
> translatable. I've changed it to elog(DEBUG2, ...) in the attached
> patch, consistent with PrepareRedoAdd() and PrepareRedoRemoveFull().

Thanks for updating the patch! LGTM.
I've pushed it. Thanks!

Regards,

--
Fujii Masao

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jakub Wartak 2026-10-29 14:16:28 Re: enhancing pg_basebackup speeds up to ~23Gbps (small fixes + io_uring/Direct I/O)
Previous Message Manu 2026-10-29 14:10:13 Re: Logical replication: lost updates/deletes and invalid log messages caused by SnapshotDirty + concurrent updates