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

Laurenz Albe <laurenz.albe@cybertec.at>

From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Andrus <kobruleht2@hot.ee>, Michael Paquier <michael@paquier.xyz>
Cc: Thomas Munro <thomas.munro@gmail.com>, Niels Jespersen <NJN@dst.dk>, Tom Lane <tgl@sss.pgh.pa.us>, pgsql-general <pgsql-general@postgresql.org>
Date: 2021-03-17T14:48:42Z
Lists: pgsql-general
On Wed, 2021-03-17 at 15:26 +0200, Andrus wrote:
> > I think what it would be most helpful to run "process monitor", so that you get
> > a log of the system calls and errors; perhaps that shows some details that
> > we cannot get from the error message.
> > 
> 
> Process monitor shows huge number of DELETE PENDING results from CreateFile operation:
> 
> 15:22:35,1708187    postgres.exe    11800    CreateFile    C:\Program Files\PostgreSQL\13\data\pg_wal\00000001000000110000003B    DELETE PENDING    Desired Access: Read Attributes, Delete,
> Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
> 15:22:35,2713856    postgres.exe    11800    CreateFile    C:\Program Files\PostgreSQL\13\data\pg_wal\00000001000000110000003B    DELETE PENDING    Desired Access: Read Attributes, Delete,
> Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
> 
> 15:22:35,3719483    postgres.exe    11800    CreateFile    C:\Program Files\PostgreSQL\13\data\pg_wal\00000001000000110000003B    DELETE PENDING    Desired Access: Read Attributes, Delete,
> Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
> 
> 15:22:35,4723624    postgres.exe    11800    CreateFile    C:\Program Files\PostgreSQL\13\data\pg_wal\00000001000000110000003B    DELETE PENDING    Desired Access: Read Attributes, Delete,
> Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a

Doesn't look like these are error messages.

There should be error messages that correspond to the error messages you see in the PostgreSQL log.

Yours,
Laurenz Albe
-- 
Cybertec | https://www.cybertec-postgresql.com




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