Re: Make relfile tombstone files conditional on WAL level - Mailing list pgsql-hackers

From Dilip Kumar
Subject Re: Make relfile tombstone files conditional on WAL level
Date
Msg-id CAFiTN-spe6WtSm1Ovn8wEc8JX9e3YFtqeHwA4DPMQQksH6PvZw@mail.gmail.com
Whole thread Raw
In response to Re: Make relfile tombstone files conditional on WAL level  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-hackers
On Mon, May 16, 2022 at 3:24 PM Thomas Munro <thomas.munro@gmail.com> wrote:
>
> I think you can get rid of SYNC_UNLINK_REQUEST, sync_unlinkfiletag,
> mdunlinkfiletag as these are all now unused.

Correct.

> Are there any special hazards here if the plan in [1] goes ahead?

IMHO we should not have any problem.  In fact, we need this for [1]
right?  Otherwise, there is a risk of reusing the same relfilenode
within the same checkpoint cycle as discussed in [2].

> [1]
https://www.postgresql.org/message-id/flat/CA%2BTgmoYmw%3D%3DTOJ6EzYb_vcjyS09NkzrVKSyBKUUyo1zBEaJASA%40mail.gmail.com

[2] https://www.postgresql.org/message-id/CA+TgmoZZDL_2E_zuahqpJ-WmkuxmUi8+g7=dLEny=18r-+c-iQ@mail.gmail.com

-- 
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Remove support for Visual Studio 2013
Next
From: Andrew Dunstan
Date:
Subject: Re: Remove support for Visual Studio 2013