Horton
Menu

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

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
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:07:11Z
Lists: pgsql-general 
Michael Paquier <michael@paquier.xyz> writes:
> 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?

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

Ah, right.  But then this theory must be nonsense, because we did
not use NtQueryInformationFile() in v13.

			regards, tom lane

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