From: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Is WAL_DEBUG related code still relevant today? |
Date: | 2023-12-03 14:53:56 |
Message-ID: | CALj2ACW5zPMT09eqXvh2Ve7Kz02HShTwyjG+xTzkrzeKtQMnQQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Dec 3, 2023 at 4:16 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Nathan Bossart <nathandbossart(at)gmail(dot)com> writes:
> > On Sat, Dec 02, 2023 at 07:36:29PM +0530, Bharath Rupireddy wrote:
> >> I started to think if this code is needed at all in production. How
> >> about we do either of the following?
>
> > Well, the fact that this code is hidden behind an off-by-default macro
> > seems like a pretty strong indicator that it is not intended for
> > production. But that doesn't mean we should remove it.
>
> Agreed, production is not the question here. The question is whether
> it's of any use to developers either. It looks to me that the code's
> been broken since v13, if not before, which very strongly suggests
> that nobody is using it. Think I'd vote for nuking it rather than
> putting effort into fixing it.
How about something like the attached? Please see the commit message
for more detailed information.
--
Bharath Rupireddy
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
Attachment | Content-Type | Size |
---|---|---|
v1-0001-Remove-WAL_DEBUG-related-code.patch | application/x-patch | 12.9 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Bharath Rupireddy | 2023-12-03 15:00:24 | Re: Is WAL_DEBUG related code still relevant today? |
Previous Message | Joe Conway | 2023-12-03 14:53:49 | Re: Emitting JSON to file using COPY TO |