model-writtenrun 7650 - may be wrong, links go to the source messages. Commit-by-commit LLM analysis is in the Commits dialog.
- Yaroslav reported frequent WAL-file permission and rename failures after upgrading four Windows Server 2019 clusters from PostgreSQL 9.6 to 13.2, despite checking permissions and antivirus exclusions #1.
- Michael Paquier reproduced the problem under pgbench without replication #3 and connected the report to other PostgreSQL 13 WAL-recycling failures #4.
- Michael supplied a revert restoring the Windows rename() path and requested comparison against unpatched 13.2 #5, subsequently providing patched and unpatched binaries for testing #10.
- Yaroslav reported no WAL-access errors over 17–20 hours with the patched build #14, while unpatched builds failed after roughly one to three hours #17; Andres Freund also requested hard-link diagnostics #13, but the diagnostic tool itself encountered access denial #16.
- Tom Lane supported restoring HAVE_WORKING_LINK while preserving the existing function name, and found no need to restore its separate pg_standby use #20; Michael incorporated this narrower scope into the second patch #22.
- Andres requested documentation of the concurrency problem and removal of the speculative file-existence-check comment #23, Tom approved the revised patch #24, and Michael agreed to the comment changes #25.
- Michael committed the second patch with documentation edits as 909b449e00, restoring Windows rename() behavior and backpatching the fix for PostgreSQL 13.3 #27.
- Yaroslav confirmed that WAL errors had disappeared and replication worked across eight production and development clusters with four replication slots, although temporary-statistics-file rename failures remained #28; Michael identified those as a separate unresolved issue and asked whether they also occurred before PostgreSQL 13 #29.