pgsql: Don't use "cp -i" in the example WAL archive_command.

Поиск
Список
Период
Сортировка
От Tom Lane
Тема pgsql: Don't use "cp -i" in the example WAL archive_command.
Дата
Msg-id E1QXiEk-000683-TP@gemulon.postgresql.org
обсуждение исходный текст
Список pgsql-committers
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.

Branch
------
REL9_1_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/c1c4f93056ceba4dcbb7779e5215e190587bea90

Modified Files
--------------
doc/src/sgml/backup.sgml |   25 +++++++++++++------------
1 files changed, 13 insertions(+), 12 deletions(-)


В списке pgsql-committers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: pgsql: Don't use "cp -i" in the example WAL archive_command.
Следующее
От: hinoue@pgfoundry.org (User Hinoue)
Дата:
Сообщение: psqlodbc - psqlodbc: Now SQLDescribeCol() can detect the changes of