Re: PostgreSQL occasionally unable to rename WAL files (NTFS)

From: Thomas Kellerer <shammat(at)gmx(dot)net>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: PostgreSQL occasionally unable to rename WAL files (NTFS)
Date: 2021-02-16 11:22:36
Message-ID: ff8ec583-b202-bebb-4c70-8b4b338f8304@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Guy Burgess schrieb am 15.02.2021 um 11:52:
> The mystery now is that the only process logged as touching the
> affected WAL files is postgres.exe (of which there are many separate
> processes). Could it be that one of the postgres.exe instances is
> holding the affected WAL files in use after another postgres.exe
> instance has flagged the file as deleted? (or to put it the other
> way, a postgres.exe instance is flagging the file as deleted while
> another instance still has an open handle to the file)? If it is some
> other process such as the indexer (disabled) or AV (excluded from
> pgdata) is obtaining a handle on the WAL files, it isn't being logged
> by ProcMon.

My first suspect is always the anti-virus on Windows when things like
that happen with Postgres.

Maybe the AV configuration was changed and pgdata is no longer excluded.

Thomas

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Paolo Saudin 2021-02-16 12:10:54 Re: Replication sequence
Previous Message Guy Burgess 2021-02-16 10:29:01 Re: PostgreSQL occasionally unable to rename WAL files (NTFS)