pgsql: Don't abort pg_basebackup when receiving empty WAL block - Mailing list pgsql-committers

From Magnus Hagander
Subject pgsql: Don't abort pg_basebackup when receiving empty WAL block
Date
Msg-id E1Vfriw-0000xV-LC@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Don't abort pg_basebackup when receiving empty WAL block

This can happen exactly at the switch of a logical WAL file
(segment number ending in FE), when running pg_basebackup connected
to a standby server, and would cause the backup to abort with
the error message "streaming header too small".

There is nothing wrong with an empty message, it's just unnecessary,
and the rest of the code can handle the case of an empty message,
so this patch just removes the error condition when the size is
exactly zero.

Branch
------
REL9_2_STABLE

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

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


pgsql-committers by date:

Previous
From: Andres Freund
Date:
Subject: Re: pgsql: Ensure that XLOG_HEAP2_VISIBLE always targets an initialized pag
Next
From: Thom Brown
Date:
Subject: Re: pgsql: doc: Clarify under what circumstances pg_dump needs superuser ac