aboutsummaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2021-03-12 12:20:15 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2021-03-12 12:20:15 -0500
commit8915e79067d666793bcf9e8f5383d41e9ee50f3e (patch)
treebc19211fea13b28eda0f2717f3c52fd83f082e79 /src
parente5794cd593940e48710693c0cdd97c6d7b91f500 (diff)
downloadpostgresql-8915e79067d666793bcf9e8f5383d41e9ee50f3e.tar.gz
postgresql-8915e79067d666793bcf9e8f5383d41e9ee50f3e.zip
Fix race condition in psql \e's detection of file modification.
psql's editing commands decide whether the user has edited the file by checking for change of modification timestamp. This is probably fine for a pre-existing file, but with a temporary file that is created within the command, it's possible for a fast typist to save-and-exit in less than the one-second granularity of stat(2) timestamps. On Windows FAT filesystems the granularity is even worse, 2 seconds, making the race a bit easier to hit. To fix, try to set the temp file's mod time to be two seconds ago. It's unlikely this would fail, but then again the race condition itself is unlikely, so just ignore any error. Also, we might as well check the file size as well as its mod time. While this is a difficult bug to hit, it still seems worth back-patching, to ensure that users' edits aren't lost. Laurenz Albe, per gripe from Jacob Champion; based on fix suggestions from Jacob and myself Discussion: https://postgr.es/m/0ba3f2a658bac6546d9934ab6ba63a805d46a49b.camel@cybertec.at
Diffstat (limited to 'src')
-rw-r--r--src/bin/psql/command.c27
1 files changed, 24 insertions, 3 deletions
diff --git a/src/bin/psql/command.c b/src/bin/psql/command.c
index 407bbd7c8c6..a840ac18721 100644
--- a/src/bin/psql/command.c
+++ b/src/bin/psql/command.c
@@ -11,6 +11,7 @@
#include <ctype.h>
#include <time.h>
#include <pwd.h>
+#include <utime.h>
#ifndef WIN32
#include <sys/stat.h> /* for stat() */
#include <fcntl.h> /* open() flags */
@@ -3619,7 +3620,6 @@ do_edit(const char *filename_arg, PQExpBuffer query_buf,
const char *fname;
bool error = false;
int fd;
-
struct stat before,
after;
@@ -3644,13 +3644,13 @@ do_edit(const char *filename_arg, PQExpBuffer query_buf,
!ret ? strerror(errno) : "");
return false;
}
+#endif
/*
* No canonicalize_path() here. EDIT.EXE run from CMD.EXE prepends the
* current directory to the supplied path unless we use only
* backslashes, so we do that.
*/
-#endif
#ifndef WIN32
snprintf(fnametmp, sizeof(fnametmp), "%s%spsql.edit.%d.sql", tmpdir,
"/", (int) getpid());
@@ -3699,6 +3699,24 @@ do_edit(const char *filename_arg, PQExpBuffer query_buf,
psql_error("%s: %s\n", fname, strerror(errno));
error = true;
}
+ else
+ {
+ struct utimbuf ut;
+
+ /*
+ * Try to set the file modification time of the temporary file
+ * a few seconds in the past. Otherwise, the low granularity
+ * (one second, or even worse on some filesystems) that we can
+ * portably measure with stat(2) could lead us to not
+ * recognize a modification, if the user typed very quickly.
+ *
+ * This is a rather unlikely race condition, so don't error
+ * out if the utime(2) call fails --- that would make the cure
+ * worse than the disease.
+ */
+ ut.modtime = ut.actime = time(NULL) - 2;
+ (void) utime(fname, &ut);
+ }
}
}
@@ -3718,7 +3736,10 @@ do_edit(const char *filename_arg, PQExpBuffer query_buf,
error = true;
}
- if (!error && before.st_mtime != after.st_mtime)
+ /* file was edited if the size or modification time has changed */
+ if (!error &&
+ (before.st_size != after.st_size ||
+ before.st_mtime != after.st_mtime))
{
stream = fopen(fname, PG_BINARY_R);
if (!stream)