aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2011-06-17 19:13:25 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2011-06-17 19:13:25 -0400
commit26996cf78e27e7bd0feb51a51a5a65308290bc5e (patch)
treea8e2d2c224fd754ead0b11f6ac17624c7b8b3580 /src/backend/access/gist
parent6c320b8ab84584e8f21cf8341121a47b51e4d297 (diff)
downloadpostgresql-26996cf78e27e7bd0feb51a51a5a65308290bc5e.tar.gz
postgresql-26996cf78e27e7bd0feb51a51a5a65308290bc5e.zip
Don't use "cp -i" in the example WAL archive_command.
This is a dangerous example to provide because on machines with GNU cp, it will silently do the wrong thing and risk archive corruption. Worse, during the 9.0 cycle somebody "improved" the discussion by removing the warning that used to be there about that, and instead leaving the impression that the command would work as desired on most Unixen. It doesn't. Try to rectify the damage by providing an example that is safe most everywhere, and then noting that you can try cp -i if you want but you'd better test that. In back-patching this to all supported branches, I also added an example command for Windows, which wasn't provided before 9.0.
Diffstat (limited to 'src/backend/access/gist')
0 files changed, 0 insertions, 0 deletions