Re: PG 11 JIT deform failure - Mailing list pgsql-hackers

From Tom Lane
Subject Re: PG 11 JIT deform failure
Date
Msg-id 9352.1560448015@sss.pgh.pa.us
Whole thread Raw
In response to PG 11 JIT deform failure  (didier <did447@gmail.com>)
Responses Re: PG 11 JIT deform failure
List pgsql-hackers
didier <did447@gmail.com> writes:
> JIT slot_compile_deform assumes there's at least  'natts' in TupleDesc, eg
>         /*
>          * Iterate over each attribute that needs to be deformed, build code to
>          * deform it.
>          */
>         for (attnum = 0; attnum < natts; attnum++)
>         {
>                 Form_pg_attribute att = TupleDescAttr(desc, attnum);

> but a new TupleDesc has no attribute and the caller only tests
> TupleDesc is not null.

I looked at this, but I find it quite unconvincing.  Under what
circumstances would we not have a correctly filled-in tupdesc here?

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: Multivariate MCV stats can leak data to unprivileged users
Next
From: Alvaro Herrera
Date:
Subject: Re: upgrades in row-level locks can deadlock