]> granicus.if.org Git - postgresql/commit
Don't abort pg_basebackup when receiving empty WAL block
authorMagnus Hagander <magnus@hagander.net>
Mon, 11 Nov 2013 13:59:55 +0000 (14:59 +0100)
committerMagnus Hagander <magnus@hagander.net>
Mon, 11 Nov 2013 14:00:33 +0000 (15:00 +0100)
commit8e41c621a625f154e96f40ce688a036520cb59aa
treef5ea2e3b23dba7a564a31d866ac03ee11bde739a
parentfc545a2548a4a2be1a66c6a4a8c36ee7b4dc264c
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.
src/bin/pg_basebackup/receivelog.c