Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lNGs8-0000sx-TH for pgsql-bugs@arkaria.postgresql.org; Fri, 19 Mar 2021 15:17:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lNGs7-0001om-T4 for pgsql-bugs@arkaria.postgresql.org; Fri, 19 Mar 2021 15:17:07 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lNGp4-0006my-FQ for pgsql-bugs@lists.postgresql.org; Fri, 19 Mar 2021 15:13:58 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lNGp1-0005U3-D7 for pgsql-bugs@lists.postgresql.org; Fri, 19 Mar 2021 15:13:58 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 12JFDqXG4065520; Fri, 19 Mar 2021 11:13:52 -0400 From: Tom Lane To: Michael Paquier cc: =?utf-8?B?0K/RgNC+0YHQu9Cw0LIg0J/QsNGI0LjQvdGB0LrQuNC5?= , Postgres bugs Subject: Re: BUG #16927: Postgres can`t access WAL files In-reply-to: References: Comments: In-reply-to Michael Paquier message dated "Fri, 19 Mar 2021 20:36:19 +0900" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4065518.1616166832.1@sss.pgh.pa.us> Date: Fri, 19 Mar 2021 11:13:52 -0400 Message-ID: <4065519.1616166832@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Michael Paquier writes: > There was a typo in one of my previous messages. What I was referring > to is aaa3aedd. Ah, I was just about to ask what the heck aaaef7a referred to. Given the evidence that there's a problem, I agree with reverting that. I'd suggest keeping the cosmetic rename of the function, but we have to put back the Windows-doesn't-HAVE_WORKING_LINK logic. Grepping in the v12 branch, I find a second use of HAVE_WORKING_LINK in contrib/pg_standby. But that seems to be in a non-WIN32 code path, so I don't think putting that back is necessary. regards, tom lane