Re: BUG #14928: Unchecked SearchSysCacheCopy1() return value
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
Cc: bianpan2016@163.com, pgsql-bugs@postgresql.org
Date: 2017-11-28T00:25:49Z
Lists: pgsql-bugs
Amit Langote <Langote_Amit_f8@lab.ntt.co.jp> writes: > On 2017/11/27 18:13, bianpan2016@163.com wrote: >> Function SearchSysCacheCopy1() may return a NULL pointer if there is no >> enough memory. But in function ATExecDetachPartition(), its return value is >> not checked, which may result in NULL dereference (see line 13818). > Thanks for the report. Attached a patch that adds a check that tuple is > valid before trying to dereference it. Pushed. Checking other SearchSysCache calls in these two files, I noted a third instance of the same problem in StorePartitionKey(). However, looking closer, StorePartitionKey never does anything at all with the result of its SearchSysCache1(PARTRELID, ...) lookup, including never releasing the syscache reference. How is it that we don't get refcount leak warnings? I guess that must prove that that lookup always fails, which is not too surprising since it seems to be against the partition key info that we haven't stored yet. Anyway, I just diked that one out, since it's clearly useless. regards, tom lane
Commits
-
Fix assorted syscache lookup sloppiness in partition-related code.
- cb03fa33aeae 11.0 landed
- 64487044966d 10.2 landed