On 25 May 2012 14:13, Magnus Hagander <mag...@hagander.net> wrote: > Here's a patch that does the two easy fixes: > 1) writes the file to a temp file and rename()s it over the main file > as it writes down. This removes the (small) risk of corruption because > of a crash during write > > 2) unlinks the file after reading it. this makes sure it's not > included in online backups.
Seems reasonable. It might be better to consistently concatenate the string literals PGSS_DUMP_FILE and ".tmp" statically. Also, I'd have updated the string in the errmsg callsite after the "error" tag too, to refer to the tmp file rather than the file proper. Forgive the pedantry, but I should mention that I believe that it is project policy to not use squiggly parenthesis following an if expression when that is unnecessary due to there only being a single statement. > I still think we should consider the placement of this file to not be > in the global/ directory, but this is a quick (back-patchable) fix... Where do you suggest the file be written to? -- Peter Geoghegan http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training and Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
