Fix error handling of XLogReaderAllocate in case of OOM
authorFujii Masao <fujii@postgresql.org>
Fri, 3 Apr 2015 12:55:37 +0000 (21:55 +0900)
committerFujii Masao <fujii@postgresql.org>
Fri, 3 Apr 2015 12:55:37 +0000 (21:55 +0900)
commit6e4bf4ecd3c2a266870139462a079809dfe7ab8c
tree8e363162645de6b1826003944e3b9a93e1a28e26
parentf85155e18cb71a599724536e598e8d6f5e140454
Fix error handling of XLogReaderAllocate in case of OOM

Similarly to previous fix 9b8d478, commit 2c03216 has switched
XLogReaderAllocate() to use a set of palloc calls instead of malloc,
causing any callers of this function to fail with an error instead of
receiving a NULL pointer in case of out-of-memory error. Fix this by
using palloc_extended with MCXT_ALLOC_NO_OOM that will safely return
NULL in case of an OOM.

Michael Paquier, slightly modified by me.
src/backend/access/transam/xlog.c
src/backend/access/transam/xlogreader.c
src/backend/replication/logical/logical.c
src/bin/pg_rewind/parsexlog.c