I don't think it's possible. however, what is possible and achieves
roughly the same affect is to query the system catalogs (or
information schema) and via dynamic sql cut trigger
funtions/procedures by looping the results of your query. non-dynamic
sql will usually be a bit faster than dynamic
I have scanned the archives and found the following message from 2004
dealing with v7.4, however it doesn't solve all my problems:
http://archives.postgresql.org/pgsql-sql/2004-07/msg00208.php
Here is a brief example. I have a table db with a merge trigger given
below, shamelessly stolen from E
On 7/31/06, Worky Workerson <[EMAIL PROTECTED]> wrote:
I'm trying to trigger a whole bunch of partitions at once (initial DB
setup) using the same plpgsql trigger. The trigger is basically the
merge trigger in the docs (i.e. UPDATE IF NOT FOUND RETURN NEW ...).
I need to use the TG_RELNAME vari
I'm trying to trigger a whole bunch of partitions at once (initial DB
setup) using the same plpgsql trigger. The trigger is basically the
merge trigger in the docs (i.e. UPDATE IF NOT FOUND RETURN NEW ...).
I need to use the TG_RELNAME variable within the "UPDATE" in the
trigger so that I can us
