Postgres Pro
Downloads
Home   >   mailing lists

Re: Possible pointer var TupleDesc rettupdesc used not initialized (src/backend/optimizer/util/clauses.c) - Mailing list pgsql-hackers

From Zhihong Yu
Subject Re: Possible pointer var TupleDesc rettupdesc used not initialized (src/backend/optimizer/util/clauses.c)
Date
Msg-id CALNJ-vTiX30nGQiZ1JGzu6OiSTgCAek=vPhniHnb_3P0V1LBEg@mail.gmail.com
Whole thread Raw
In response to Re: Possible pointer var TupleDesc rettupdesc used not initialized (src/backend/optimizer/util/clauses.c)  (Ranier Vilela <ranier.vf@gmail.com>)
Responses Re: Possible pointer var TupleDesc rettupdesc used not initialized (src/backend/optimizer/util/clauses.c)
List pgsql-hackers
Tree view


On Mon, May 24, 2021 at 7:21 PM Ranier Vilela <ranier.vf@gmail.com> wrote:
Em seg., 24 de mai. de 2021 às 22:42, Mark Dilger <mark.dilger@enterprisedb.com> escreveu:


> On May 24, 2021, at 5:37 PM, Ranier Vilela <ranier.vf@gmail.com> wrote:
>
> Hi,
>
> Possible pointer TupleDesc rettupdesc used not initialized?
>
> if (!isNull) at line 4346 taking a true branch, the function check_sql_fn_retval at line 4448 can use rettupdesc uninitialized.

Care to submit a patch?
Hi Mark, sorry but not.
I examined the code and I can't say what the correct value is for rettupdesc.

Hi,
It seems the following call would fill up value for rettupdesc :

functypclass = get_expr_result_type((Node *) fexpr, NULL, &rettupdesc); 

Cheers

regards,
Ranier Vilela

Livre de vírus. www.avast.com.

pgsql-hackers by date:

Previous
From: Ranier Vilela
Date:
Subject: Re: Possible pointer var TupleDesc rettupdesc used not initialized (src/backend/optimizer/util/clauses.c)
Next
From: Ajin Cherian
Date:
Subject: Re: [HACKERS] logical decoding of two-phase transactions