From: Peter Eisentraut Date: Thu, 27 Feb 2020 15:33:05 +0000 (+0100) Subject: pg_standby: Don't use HAVE_WORKING_LINK X-Git-Tag: REL_13_BETA1~622 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=1810ca18bfad9072facc548417630115b078483e;p=thirdparty%2Fpostgresql.git pg_standby: Don't use HAVE_WORKING_LINK HAVE_WORKING_LINK is meant to indicate support for hard links, mainly for Windows. Here it is used for soft links on Unix, and the functionality is optional anyway, so we can just make it error out normally if needed. Discussion: https://www.postgresql.org/message-id/flat/72fff73f-dc9c-4ef4-83e8-d2e60c98df48%402ndquadrant.com --- diff --git a/contrib/pg_standby/pg_standby.c b/contrib/pg_standby/pg_standby.c index 74149060a90..c9f33e4254c 100644 --- a/contrib/pg_standby/pg_standby.c +++ b/contrib/pg_standby/pg_standby.c @@ -144,10 +144,8 @@ CustomizableInitialize(void) switch (restoreCommandType) { case RESTORE_COMMAND_LINK: -#ifdef HAVE_WORKING_LINK SET_RESTORE_COMMAND("ln -s -f", WALFilePath, xlogFilePath); break; -#endif case RESTORE_COMMAND_COPY: default: SET_RESTORE_COMMAND("cp", WALFilePath, xlogFilePath);