database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-28 23:42:10 +03:00
Code Activity

Improve copydir() code for the case that fsync is off.

Browse Source 
We should avoid calling sync_file_range or posix_fadvise in this case,
since (a) we don't really care if the data gets synced, and might as
well save the kernel calls; (b) at least on Linux we know that the
kernel might block us until it's scheduled the write.

Also, avoid making a useless second traversal of the directory tree
if we're not actually going to call fsync(2) after all.
This commit is contained in:
Tom Lane
2012-07-21 20:10:29 -04:00
parent 2c4f5b4bc5
commit 2d46a57ddc
2 changed files with 15 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
src/backend/storage/file/copydir.c
View File

@ -98,7 +98,11 @@ copydir(char *fromdir, char *todir, bool recurse)
/*
* Be paranoid here and fsync all files to ensure the copy is really done.
* But if fsync is disabled, we're done.
*/
if (!enableFsync)
return;
xldir = AllocateDir(todir);
if (xldir == NULL)
ereport(ERROR,
@ -200,9 +204,9 @@ copy_file(char *fromfile, char *tofile)
/*
* We fsync the files later but first flush them to avoid spamming the
* cache and hopefully get the kernel to start writing them out before
* the fsync comes.
* the fsync comes. Ignore any error, since it's only a hint.
*/
pg_flush_data(dstfd, offset, nbytes);
(void) pg_flush_data(dstfd, offset, nbytes);
}
if (close(dstfd))