Re: BUG #16927: Postgres can`t access WAL files
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Magnus Hagander <magnus@hagander.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Ярослав Пашинский <yarik97.6@gmail.com>, Postgres bugs <pgsql-bugs@lists.postgresql.org>
Date: 2021-03-19T22:32:43Z
Lists: pgsql-bugs
Attachments
- win32-link.patch (text/x-diff) patch
On Fri, Mar 19, 2021 at 04:19:50PM +0100, Magnus Hagander wrote: > On Fri, Mar 19, 2021 at 4:14 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: >> 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. > > +1. I think the indications are definitely clear enough that this has > to go back in. No problem from me to keep the rename, and so this leads to the simple patch attached, then. Any comments? >> 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. > > .. and apart front aht I *really* doubt that one has many users, > especially on Windows :) Yeah, agreed. -- Michael
Commits
-
Fix concurrency issues with WAL segment recycling on Windows
- 78c24e97dd18 13.3 landed
- 909b449e00fc 14.0 landed