]> granicus.if.org Git - postgresql/commit
projects / postgresql / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 001e114) | patch
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 13:59:55 +0000 (14:59 +0100)
commit705556a631c5908cd3caa0b973be13d994ff63e7
treee69eb3a07cd209f37045ef1272594b27cc83ba33tree | snapshot
parent001e114b8d59f4eaf2a314a2bc5e57078afdf82fcommit | diff
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 diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.