Re: HAVE_WORKING_LINK still needed?
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2020-02-28T15:03:23Z
Lists: pgsql-hackers
On 2020-Feb-28, Peter Eisentraut wrote:
> @@ -788,7 +788,6 @@ durable_link_or_rename(const char *oldfile, const char *newfile, int elevel)
> if (fsync_fname_ext(oldfile, false, false, elevel) != 0)
> return -1;
>
> -#ifdef HAVE_WORKING_LINK
> if (link(oldfile, newfile) < 0)
> {
> ereport(elevel,
> @@ -798,17 +797,6 @@ durable_link_or_rename(const char *oldfile, const char *newfile, int elevel)
> return -1;
> }
> unlink(oldfile);
> -#else
> - /* XXX: Add racy file existence check? */
> - if (rename(oldfile, newfile) < 0)
Maybe rename durable_link_or_rename to just durable_link?
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Remove HAVE_WORKING_LINK
- aaa3aeddee51 13.0 landed
-
Move pg_upgrade's Windows link() implementation to AC_REPLACE_FUNCS
- 0ad6f848eef2 13.0 landed
-
pg_standby: Don't use HAVE_WORKING_LINK
- 1810ca18bfad 13.0 landed
-
Update Microsoft documentation link
- ed0d88376589 13.0 landed