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

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Don't abort pg_basebackup when receiving empty WAL block
Date: 2013-11-11 13:40:14
Message-ID: E1Vfriw-0000xV-LC@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Thom Brown 2013-11-11 13:48:04 Re: pgsql: doc: Clarify under what circumstances pg_dump needs superuser ac
Previous Message Tom Lane 2013-11-10 23:12:20 Re: [COMMITTERS] pgsql: Replace duplicate_oids with Perl implementation