Re: Use XLOG_CONTROL_FILE macro everywhere?

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: "Anton A(dot) Melnikov" <a(dot)melnikov(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Use XLOG_CONTROL_FILE macro everywhere?
Date: 2024-04-20 06:36:58
Message-ID: EC05A03A-36A5-4188-8E54-458620A2359E@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 20 Apr 2024, at 01:23, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Fri, Apr 19, 2024 at 10:12:14AM +0200, Daniel Gustafsson wrote:
>> Off the cuff that seems to make sense, it does make it easier to grep for uses
>> of the control file.
>
> +1 for switching to the macro where we can. Still, I don't see a
> point in rushing and would just switch that once v18 opens up for
> business.

Absolutely, this is not fixing a defect so it's v18 material.

Anton: please register this patch in the Open commitfest to ensure it's not
forgotten about.

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2024-04-20 09:03:21 Re: Remove deprecated header file resowner_private.h.
Previous Message Thomas Munro 2024-04-20 05:56:00 Re: fix tablespace handling in pg_combinebackup