Re: SV: Log files polluted with permission denied error messages after every 10 seconds

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andrus <kobruleht2@hot.ee>, Laurenz Albe <laurenz.albe@cybertec.at>, Thomas Munro <thomas.munro@gmail.com>, Niels Jespersen <NJN@dst.dk>, pgsql-general <pgsql-general@postgresql.org>
Date: 2021-03-17T21:00:03Z
Lists: pgsql-general
On Wed, Mar 17, 2021 at 11:44:48AM -0400, Tom Lane wrote:
> Oh!  That's an interesting theory; it'd explain why this broke recently,
> because we didn't use to use that function.  But how do you draw that
> conclusion from this stack trace?
> 
> Anyway, if you've diagnosed this correctly, I bet the fault is in
> this bit in win32stat.c:
> 
> #if _WIN32_WINNT < 0x0600
> 	IO_STATUS_BLOCK ioStatus;
> 	FILE_STANDARD_INFORMATION standardInfo;
> #else
> 	FILE_STANDARD_INFO standardInfo;
> #endif
> 
> Maybe the version cutoff is wrong?  Maybe we have to do this with
> a run-time version check, instead of statically compiling it?

All the reports received are on 13.1 and 13.2.  This code is new as of
bed9075, no?
--
Michael

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Fix concurrency issues with WAL segment recycling on Windows