Re: Is WAL_DEBUG related code still relevant today? - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Is WAL_DEBUG related code still relevant today?
Date
Msg-id ZXKfXjHhikO8yeIx@paquier.xyz
Whole thread Raw
In response to Re: Is WAL_DEBUG related code still relevant today?  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
Responses Re: Is WAL_DEBUG related code still relevant today?
List 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

Attachment

pgsql-hackers by date:

Previous
From: Andrei Lepikhov
Date:
Subject: Re: Assert failure on 'list_member_ptr(rel->joininfo, restrictinfo)'
Next
From: John Naylor
Date:
Subject: Re: micro-optimizing json.c