| From: | "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> |
|---|---|
| To: | "James Mansion" <james(at)mansionfamily(dot)plus(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal for db level triggers |
| Date: | 2008-03-14 11:16:28 |
| Message-ID: | 2e78013d0803140416m2ef3093dh1f064398a9dbcece@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Mar 14, 2008 at 3:44 AM, James Mansion
<james(at)mansionfamily(dot)plus(dot)com> wrote:
>
> And if we use data update triggers to insert into a DELETE ROWS temp
> table or an in-memory data
> structure, the BEFORE COMMIT trigger is the place to do a bulk copy into
> real table(s) or combine
> rows into a BLOb in an audit table.
>
Another use case of BEFORE COMMIT trigger is to update the row counts
for fast select count(*) operations (of course with some additional
infrastructure)
Thanks,
Pavan
--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paul van den Bogaard | 2008-03-14 13:02:05 | Re: Reducing Transaction Start/End Contention |
| Previous Message | Pavan Deolasee | 2008-03-14 09:16:01 | Re: PROC_VACUUM_FOR_WRAPAROUND doesn't work expectedly |