Re: [BUGS] BUG #14799: SELECT * FROM transition_table in a statement-level trigger
От | Tom Lane |
---|---|
Тема | Re: [BUGS] BUG #14799: SELECT * FROM transition_table in a statement-level trigger |
Дата | |
Msg-id | 18696.1504704754@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | [BUGS] BUG #14799: SELECT * FROM transition_table in a statement-leveltrigger (phb07@apra.asso.fr) |
Ответы |
Re: [BUGS] BUG #14799: SELECT * FROM transition_table in astatement-level trigger
|
Список | pgsql-bugs |
phb07@apra.asso.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 -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
В списке pgsql-bugs по дате отправления: