Re: [PATCH][BUG_FIX] Potential null pointer dereferencing. - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: [PATCH][BUG_FIX] Potential null pointer dereferencing.
Date
Msg-id 630747A0-D258-4AF6-B6E1-3AFABDB2B990@yesql.se
Whole thread Raw
In response to [PATCH][BUG_FIX] Potential null pointer dereferencing.  (Ranier Vilela <ranier_gyn@hotmail.com>)
Responses RE: [PATCH][BUG_FIX] Potential null pointer dereferencing.  (Ranier Vilela <ranier_gyn@hotmail.com>)
List pgsql-hackers
> On 12 Nov 2019, at 14:07, Ranier Vilela <ranier_gyn@hotmail.com> wrote:

> ExecClearTuple don't check por NULL pointer arg and according
> TupIsNull slot can be NULL.

I assume you are referring to the TupIsNull(resultTupleSlot) check a few lines
down in the same loop?  If resultTupleSlot was indeed NULL and not empty, the
subsequent call to ExecCopySlot would be a NULL pointer dereference too.  I
might be missing something obvious, but in which case can resultTupleSlot be
NULL when calling ExecUnique?

cheers ./daniel


pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: [HACKERS] Block level parallel vacuum
Next
From: Ranier Vilela
Date:
Subject: RE: [PATCH][BUG_FIX] Potential null pointer dereferencing.