Re: Back patch of Remove durable_rename_excl()

2025-01-29 Thread Nitin Jadhav
Thank you for providing the details. I agree to the concern about breaking extensions that depend on the function. Gradually phasing it out as versions become unsupported seems like a sensible approach. Best Regards, Nitin Jadhav Azure Database for PostgreSQL Microsoft On Mon, Jan 27, 2025 at 8:4

Re: Back patch of Remove durable_rename_excl()

2025-01-27 Thread Nathan Bossart
On Mon, Jan 27, 2025 at 09:47:22AM -0500, Tom Lane wrote: > Nitin Jadhav 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() >

Re: Back patch of Remove durable_rename_excl()

2025-01-27 Thread Tom Lane
Nitin Jadhav 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 corrup

Back patch of Remove durable_rename_excl()

2025-01-27 Thread Nitin Jadhav
Hi, 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 i