model-writtenrun 9688 - may be wrong, links go to the source messages. Commit-by-commit LLM analysis is in the Commits dialog.
- John Klann reported that PostgreSQL 11.1 pg_basebackup and parallel pg_dump produced directory fsync errors on CIFS, while local storage and NFS worked, and asked about backup integrity and workarounds in #1.
- Thomas Munro traced the failure to older Linux CIFS returning EINVAL for directory fsync and proposed treating it like the already tolerated EBADF in #2; he supplied the two-function patch in #4.
- After Thomas supplied build instructions in #6, John demonstrated that the patch removed the backup error and that the resulting backup restored successfully in #8.
- Thomas questioned whether PostgreSQL should accommodate an issue already fixed in newer kernels in #9, while Michael Paquier warned that ignoring EINVAL could conceal invalid operations in #10; Thomas explained that the exception applied only to directories in #11.
- Michael remained mildly opposed to back-patching in #12, but Stephen Frost argued that directory synchronization being unsupported was distinct from an I/O failure and that disabling all fsync calls was an unsuitable workaround in #13.
- Separately, Stephen warned that John's archive_command could acknowledge incompletely persisted WAL and jeopardize recovery in #14, which John acknowledged in #15; the directory-fsync patch did not address that configuration issue.
- Thomas revisited the unresolved compatibility decision in #16, and Andres Freund supported tolerating EINVAL because it did not appear to indicate data-level failures and older kernels would remain common in #17.
- Thomas committed the unchanged code from #4 as f16735d80d, with backports to all supported branches, and confirmed the push in the final message #18; no patch revisions remained pending.