2010/10/21 Grzegorz JaÅkiewicz <gryzman@xxxxxxxxx>: > OLD.column_name > NEW.column_name ? I believe OP is asking specifically about statement-level triggers. As the docs <http://www.postgresql.org/docs/current/static/trigger-definition.html> say: | Statement-level triggers do not currently have any way to | examine the individual row(s) modified by the statement. What I've done is to have a row-level trigger that populates a temporary table with "interesting" changes that need further processing, and then a statement-level trigger which does bulk-updates based on what's in that temporary table. This comes in quite handy when bulk-loading data, e.g. with COPY. Josh -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
