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
