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

Guy Burgess <guy@burgess.co.nz>

From: Guy Burgess <guy@burgess.co.nz>
To: Michael Paquier <michael@paquier.xyz>
Cc: Andrus <kobruleht2@hot.ee>, Laurenz Albe <laurenz.albe@cybertec.at>, pgsql-general <pgsql-general@postgresql.org>, Thomas Munro <thomas.munro@gmail.com>, Niels Jespersen <NJN@dst.dk>, Tom Lane <tgl@sss.pgh.pa.us>
Date: 2021-03-18T00:19:54Z
Lists: pgsql-general
Thanks - yes pleas send me a private link and I will try to reproduce it 
in a test environment and then test the patch.

Regards,

Guy


On 18/03/2021 1:08 pm, Michael Paquier wrote:
> On Thu, Mar 18, 2021 at 12:25:45PM +1300, Guy Burgess wrote:
>> FWIW, this looks the same issue I am getting (reported last month:
>> https://www.postgresql.org/message-id/f444a84e-2d29-55f9-51a6-a5dcea3bc253%40burgess.co.nz)
> Yep.
>
>> I get the same Process Monitor output, including BUFFER OVERFLOW entries.
>> No sign of any process other than postgres.exe touching the WAL files.
> Guy, do you have an environment where this is still happening and
> where you could test a potential fix?  We are not sure yet what's
> causing that, but one code path has changed in this area, involving
> CreateHardLinkA()+_unlink() instead of a single rename when attempting
> to recycle a segment.  And I am just in a mood to build things by
> myself and send some links to people to be able to download and test
> that, so one more is fine..
> --
> 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