| From: | Amit Khandekar <amit(dot)khandekar(at)enterprisedb(dot)com> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, David Fetter <david(at)fetter(dot)org>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: delta relations in AFTER triggers |
| Date: | 2014-08-14 09:45:53 |
| Message-ID: | CACoZds2joQLMF2pW_axdxzk62M6PMOky-5RBPCmT208kyhkQzw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> The execution level
>> itself was almost trivial; it's getting the tuplestore reference
>> through the parse analysis and planning phases that is painful for
>> me.
> I am not sure why you think we would need to refer the tuplestore in
> the parse analysis and planner phases. It seems that we would need
> them only in execution phase. Or may be I didn't understand your
> point.
Ah I think I understand now. That might be because you are thinking of
having an infrastructure common to triggers and materialized views,
right ?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2014-08-14 09:47:19 | Re: What happened to jsonb's JENTRY_ISFIRST? |
| Previous Message | Andres Freund | 2014-08-14 09:44:46 | Re: WAL format and API changes (9.5) |