]> granicus.if.org Git - postgresql/commit
Rework handling of OOM when allocating record buffer in XLOG reader.
authorFujii Masao <fujii@postgresql.org>
Fri, 3 Apr 2015 09:29:38 +0000 (18:29 +0900)
committerFujii Masao <fujii@postgresql.org>
Fri, 3 Apr 2015 09:29:38 +0000 (18:29 +0900)
commit9b8d4782ba0f75eb0f029c743bb85166999d9fa5
treef82c476bf0b8c2b69211aa46ddb1c32a550a8d48
parent8c8a886268dfa616193dadc98e44e0715f884614
Rework handling of OOM when allocating record buffer in XLOG reader.

Commit 2c03216 changed allocate_recordbuf() so that it uses a palloc to
allocate the read buffer and fails immediately when an out-of-memory error
shows up, even though its callers still expect that NULL is returned in that
case. This bug is fixed making allocate_recordbuf() use a palloc_extended
with MCXT_ALLOC_NO_OOM flag and return NULL in OOM case.

Michael Paquier
src/backend/access/transam/xlogreader.c