Re: BUG #14799: SELECT * FROM transition_table in a statement-level trigger

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: phb07(at)apra(dot)asso(dot)fr
Cc: pgsql-bugs(at)postgresql(dot)org, Kevin Grittner <kgrittn(at)postgresql(dot)org>
Subject: Re: BUG #14799: SELECT * FROM transition_table in a statement-level trigger
Date: 2017-09-06 13:32:34
Message-ID: 18696.1504704754@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

phb07(at)apra(dot)asso(dot)fr writes:
> I am playing a bit with transition tables in statement-level triggers, using
> the postgres V10 beta 4 version. I am facing an issue that I suspect to be a
> bug (unless it is a design limitation). I have built a small test case to
> reproduce what I have discovered.
> ...
> It looks like the resolution of the column list has not taken into account a
> "NOT attisdropped" condition when scanning the pg_attribute table (or an
> equivalent in memory structure).

Yeah. The RTE_NAMEDTUPLESTORE patch seems to have piggybacked on the code
for RTE_CTE and friends, none of which could have dropped columns so the
case wasn't considered. I think the immediate problem is in expandRTE()
but I have zero faith that there aren't comparable bugs elsewhere.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Francisco Olarte 2017-09-06 14:12:41 Re: BUG #14800: substring produces different results with similar types
Previous Message Alvaro Herrera 2017-09-06 13:27:38 Re: Old row version in hot chain become visible after a freeze