Clean up some elog messages and comments for do_pg_stop_backup anddo_pg_start_backup

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Clean up some elog messages and comments for do_pg_stop_backup anddo_pg_start_backup
Дата
Msg-id 20181221040510.GA12599@paquier.xyz
обсуждение исходный текст
Ответы Re: Clean up some elog messages and comments for do_pg_stop_backupand do_pg_start_backup  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Re: Clean up some elog messages and comments for do_pg_stop_backupand do_pg_start_backup  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Список pgsql-hackers
Hi all,

Alvaro has cleaned up a couple of error messages recently so as they do
not include the function name in what gets translated as per 68f6f2b7.

While looking in the code for similar patterns, I have been reminded
that pg_stop_backup() is included in some messages when waiting for
segments to be archived.  This has resulted in an exchange between Tom
and me here:
https://www.postgresql.org/message-id/E1gZg2W-0008Lq-0w@gemulon.postgresql.org

The thing is that the current messages are actually misleading, because
for base backups taken by the replication protocol pg_stop_backup is
never called, which is I think confusing.  While looking around I have
also noticed that the top comments of do_pg_start_backup and
do_pg_stop_backup also that they are used with BASE_BACKUP.

Attached is a patch to reduce the confusion and improve the related
comments and messages.

Thoughts?
--
Michael

Вложения

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Tid scan improvements
Следующее
От: Kyotaro HORIGUCHI
Дата:
Сообщение: Re: Change pgarch_readyXlog() to return .history files first