Re: Proposal for db level triggers - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Proposal for db level triggers
Date
Msg-id 200805080145.m481jP801629@momjian.us
Whole thread Raw
In response to Re: Proposal for db level triggers  (Decibel! <decibel@decibel.org>)
List pgsql-hackers
Added to TODO:

* Add database and transaction-level triggers
 http://archives.postgresql.org/pgsql-hackers/2008-03/msg00451.php


---------------------------------------------------------------------------

Decibel! wrote:
> 
> On Mar 13, 2008, at 5:14 PM, James Mansion wrote:
> 
> > James Mansion wrote:
> >> In usage:
> >>
> >> AFTER START clears counters and flags.
> >> UPDATE triggers on data set counters and flags.
> >> BEFORE COMMIT examines the counters and flags and performs any  
> >> final validation or
> >> adjustments (or external events such as sending a MoM message)
> >>
> > I'd like to point out also that AFTER CONNECT is a good opportunity  
> > to CREATE TEMP TABLE (be
> > nice if a global temp table definition could be persisted and  
> > automatically duplicated into each session, but
> > never mind).
> 
> +1 on both counts. Can we get a TODO?
> -- 
> Decibel!, aka Jim C. Nasby, Database Architect  decibel@decibel.org
> Give your computer some brain candy! www.distributed.net Team #1828
> 
> 

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Lazy constraints / defaults
Next
From: Bruce Momjian
Date:
Subject: Re: postgresql in FreeBSD jails: proposal