Re: pgsql: Replace existing durable_rename_excl() calls with durable_rename

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Replace existing durable_rename_excl() calls with durable_rename
Date: 2022-04-28 03:28:18
Message-ID: 511362.1651116498@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Michael Paquier <michael(at)paquier(dot)xyz> writes:
> This change replaces all calls to durable_rename_excl() with
> durable_rename(). This removes the protection against accidentally
> overwriting an existing file, but some platforms are already living
> without it, and all those code paths never expect an existing file (a
> couple of assertions are added to check after that, in case).

Assert'ing that an external (filesystem) condition holds seems like a bad
idea. See buildfarm.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2022-04-28 03:48:27 Re: pgsql: Replace existing durable_rename_excl() calls with durable_rename
Previous Message Jeff Davis 2022-04-28 03:11:37 Re: pgsql: Add contrib/pg_walinspect.