Re: PG 11 JIT deform failure

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: didier <did447(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PG 11 JIT deform failure
Date: 2019-06-13 17:46:55
Message-ID: 9352.1560448015@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

didier <did447(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2019-06-13 18:00:14 Re: upgrades in row-level locks can deadlock
Previous Message Tomas Vondra 2019-06-13 17:37:45 Re: Multivariate MCV stats can leak data to unprivileged users