Re: delta relations in AFTER triggers
От | Robert Haas |
---|---|
Тема | Re: delta relations in AFTER triggers |
Дата | |
Msg-id | CA+TgmoYeB0iFaHfFMthRb-rD4RoyGZrmPwU9-+k1W4U1BoNeSg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: delta relations in AFTER triggers (Heikki Linnakangas <hlinnakangas@vmware.com>) |
Ответы |
Re: delta relations in AFTER triggers
|
Список | pgsql-hackers |
On Tue, Sep 23, 2014 at 12:46 PM, Heikki Linnakangas <hlinnakangas@vmware.com> wrote: > On 09/15/2014 05:25 PM, Kevin Grittner wrote: > Now, how do we make the tuplestores work similarly? Here's what I think we > should do: > > Add a new p_tableref_hook function pointer, similar to p_paramref_hook. > Whenever the parser sees a RangeVar that it doesn't recognize (or actually, > I think it should call it *before* resolving regular tables, but let's > ignore that for now), it calls the p_tableref_hook. It can return a new > RelationParam node (similar to regular Param), which contains a numeric ID > for the table/tuplestore, as well as its tuple descriptor. > > For the execution phase, add a new array of Tuplestorestates to > ParamListInfo. Similar to the existing array of ParamExternalDatas. I haven't been following this issue closely, but this sounds like a really nice design. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: