Horton

Re: Is WAL_DEBUG related code still relevant today?

Michael Paquier <michael@paquier.xyz>

View thread View on postgr.es
From: Michael Paquier <michael@paquier.xyz>
To: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Cc: Euler Taveira <euler@eulerto.com>, Peter Eisentraut <peter@eisentraut.org>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-12-08T04:45:18Z
Lists: pgsql-hackers 
On Thu, Dec 07, 2023 at 05:29:55PM +0530, Bharath Rupireddy wrote:
> The comment atop trace_recovery [1] function says it should go away
> eventually and seems to have served the purpose when the recovery
> related code was introduced in PG 9.0.
> 
> FWIW, the attached patch is what I've left with after removing
> trace_recovery_messages related code, 9 files changed, 19
> insertions(+), 97 deletions(-).

Looks acceptable to me.  Does somebody object to this removal?
--
Michael

Commits

  1. Remove trace_recovery_messages

  2. Fix compilation on Windows with WAL_DEBUG