| From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | Ralph Mason <ralph(dot)mason(at)telogis(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Trigger Rowsets |
| Date: | 2005-11-02 23:50:12 |
| Message-ID: | 20051102235012.GB55520@pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thu, Nov 03, 2005 at 12:34:14PM +1300, Ralph Mason wrote:
> I want to do statement level triggers for performance, but it seems
> there is no 'updated', 'inserted', or 'deleted' tables inside the
> trigger and nothing I can find in the documentation that offers similar
> functionality.
>
> Is there any way that I can access only those rows that were changed?
No. The only way you can do this is with row-level triggers. There's
also not currently any plans to allow statement-level triggers to
interact with the data that was modified by the statement.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2005-11-03 02:52:33 | Re: [PERFORM] improvise callbacks in plpgsql |
| Previous Message | Jim C. Nasby | 2005-11-02 23:44:30 | Re: [PERFORM] improvise callbacks in plpgsql |