Re: implementing an out-of-transaction trigger

>I've come across a situation where I'd like to use some kind of
"out-of-transaction
>trigger" to do some processing after changes to some tables, but
without extending
>the duration of the main transaction. Of course, it's important that
the processing be
>completed so it has to be, as far as possible, reliable and "safe". The extra
>processing should be completed within a reasonable time after the original
>transaction, but it needn't happen immediately.  
Check out http://www.postgresql.org/docs/7.4/static/sql-listen.html
and http://www.postgresql.org/docs/7.4/static/sql-notify.html

Then look at the Rules system for generating a NOTIFY:  http://www.postgresql.org/docs/7.4/static/sql-createrule.html

--miker