pgsql: Don't abort pg_basebackup when receiving empty WAL block

Поиск
Список
Период
Сортировка
От Magnus Hagander
Тема pgsql: Don't abort pg_basebackup when receiving empty WAL block
Дата
Msg-id E1Vfs32-0001Kh-SZ@gemulon.postgresql.org
обсуждение исходный текст
Список pgsql-committers
Don't abort pg_basebackup when receiving empty WAL block

This is a similar fix as c6ec8793aa59d1842082e14b4b4aae7d4bd883fd
9.2. This should never happen in 9.3 and newer since the special case
cannot happen there, but this patch synchronizes up the code so there
is no confusion on why they're different. An empty block is as harmless
in 9.3 as it was in 9.2, and can safely be ignored.

Branch
------
REL9_3_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/8e41c621a625f154e96f40ce688a036520cb59aa

Modified Files
--------------
src/bin/pg_basebackup/receivelog.c |    2 +-
1 file changed, 1 insertion(+), 1 deletion(-)


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

Предыдущее
От: Magnus Hagander
Дата:
Сообщение: pgsql: Don't abort pg_basebackup when receiving empty WAL block
Следующее
От: Tom Lane
Дата:
Сообщение: Re: pgsql: Fix whitespace issues found by git diff --check, add gitattribut