Horton
Menu

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

Andrus <kobruleht2@hot.ee>

View thread
From: Andrus <kobruleht2@hot.ee>
To: Tom Lane <tgl@sss.pgh.pa.us>, Thomas Munro <thomas.munro@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>, Laurenz Albe <laurenz.albe@cybertec.at>, pgsql-general <pgsql-general@postgresql.org>
Date: 2021-03-08T22:23:37Z
Lists: pgsql-general 
> Yeah, I've wondered for some time if the apparent EACCES code is
> actually being mapped from something other than ERROR_SHARING_VIOLATION
> in (some of?) these reports.  The hard part is to hold onto the
> Windows error code alongside errno without massively invasive changes.

Permission denied error occur in  Windows. Debian logs doesnt contain it.

In Windows also pg_database_size('mydb')  and similar ones fail 
frequently with permission denied error.

I got information about r1soft idera backup client used. It runs only 
once per night for 16 minutes and compares disk blocks to find changed 
blocks to backup. So it should not cause permission denied errors after 
every 10 seconds.

Andrus.

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