=?utf-8?q?PG_Bug_reporting_form?= <noreply(at)postgresql(dot)org> writes: > When I pg_dump a large table (> 35 GB), I get the following error message:
> pg_dump: could not stat file > "O:\postgres-server3\test#test#large_test/2793.dat.gz": Unknown error
> The dump however appears to restore correctly.
Hm, I assume this shows up just at the end of the dump run?
The only plausible match for that error string is in the fsync_dir_recurse() processing that tries to force all the output files down to disk before reporting that the dump is complete. As long as you don't have an OS crash right afterwards, failure to fsync is harmless. Still, it's weird.
Does it vary with the size of the dumped table? What if you remove the parallelism (no --jobs option)?