Re: Log files polluted with permission denied error messages after every 10 seconds
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>, Andrus <kobruleht2@hot.ee>,
Laurenz Albe <laurenz.albe@cybertec.at>,
pgsql-general <pgsql-general@postgresql.org>
Date: 2021-03-08T21:58:32Z
Lists: pgsql-general
Thomas Munro <thomas.munro@gmail.com> writes: > Another thought: if it's not a sharing violation, I wonder if we > should consider dumping more raw Windows error information in the > messages we log, because, if I recall correctly, we're converting many > Windows error codes into few Unix-style error numbers and thereby > throwing away valuable clues. It makes it a bit more confusing when > trying to ask a Windows expert what might be happening. 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. 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 →
-
Fix concurrency issues with WAL segment recycling on Windows
- 78c24e97dd18 13.3 landed
- 909b449e00fc 14.0 landed