Re: Back patch of Remove durable_rename_excl() - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Back patch of Remove durable_rename_excl()
Date
Msg-id 392265.1737989242@sss.pgh.pa.us
Whole thread Raw
In response to Back patch of Remove durable_rename_excl()  (Nitin Jadhav <nitinjadhavpostgres@gmail.com>)
Responses Re: Back patch of Remove durable_rename_excl()
List pgsql-hackers
Nitin Jadhav <nitinjadhavpostgres@gmail.com> writes:
> I noticed that the corruption issue related to two hardlinks pointing
> to the same WAL file has been fixed in the master branch up to version
> 16 in commit [1]. As a result, the function durable_rename_excl()
> became unused and was removed in commit [2]. Since this corruption
> issue is occurring in older versions, commit [1] has been backported
> for versions 13 to 15 in commit [3]. However, I don't see the
> backporting for commit [2]. Is there a specific reason for this?

Fear of breaking extensions that use the function, perhaps?
We don't like to break ABI in minor releases.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: BF member drongo doesn't like 035_standby_logical_decoding.pl
Next
From: Srinath Reddy
Date:
Subject: Re: Why we need to check for local buffers in BufferIsExclusiveLocked and BufferIsDirty?