Movatterモバイル変換


[0]ホーム

URL:



Facebook
Postgres Pro
Facebook
Downloads
40.9. Trigger Procedures
Prev UpChapter 40. PL/pgSQL -SQL Procedural LanguageHome Next

40.9. Trigger Procedures

40.9.1. Triggers on Data Changes

PL/pgSQL can be used to define trigger procedures. A trigger procedure is created with theCREATE FUNCTION command, declaring it as a function with no arguments and a return type oftrigger. Note that the function must be declared with no arguments even if it expects to receive arguments specified inCREATE TRIGGER — trigger arguments are passed viaTG_ARGV, as described below.

When aPL/pgSQL function is called as a trigger, several special variables are created automatically in the top-level block. They are:

NEW

Data typeRECORD; variable holding the new database row forINSERT/UPDATE operations in row-level triggers. This variable is unassigned in statement-level triggers and forDELETE operations.

OLD

Data typeRECORD; variable holding the old database row forUPDATE/DELETE operations in row-level triggers. This variable is unassigned in statement-level triggers and forINSERT operations.

TG_NAME

Data typename; variable that contains the name of the trigger actually fired.

TG_WHEN

Data typetext; a string ofBEFORE,AFTER, orINSTEAD OF, depending on the trigger's definition.

TG_LEVEL

Data typetext; a string of eitherROW orSTATEMENT depending on the trigger's definition.

TG_OP

Data typetext; a string ofINSERT,UPDATE,DELETE, orTRUNCATE telling for which operation the trigger was fired.

TG_RELID

Data typeoid; the object ID of the table that caused the trigger invocation.

TG_RELNAME

Data typename; the name of the table that caused the trigger invocation. This is now deprecated, and could disappear in a future release. UseTG_TABLE_NAME instead.

TG_TABLE_NAME

Data typename; the name of the table that caused the trigger invocation.

TG_TABLE_SCHEMA

Data typename; the name of the schema of the table that caused the trigger invocation.

TG_NARGS

Data typeinteger; the number of arguments given to the trigger procedure in theCREATE TRIGGER statement.

TG_ARGV[]

Data type array oftext; the arguments from theCREATE TRIGGER statement. The index counts from 0. Invalid indexes (less than 0 or greater than or equal totg_nargs) result in a null value.

A trigger function must return eitherNULL or a record/row value having exactly the structure of the table the trigger was fired for.

Row-level triggers firedBEFORE can return null to signal the trigger manager to skip the rest of the operation for this row (i.e., subsequent triggers are not fired, and theINSERT/UPDATE/DELETE does not occur for this row). If a nonnull value is returned then the operation proceeds with that row value. Returning a row value different from the original value ofNEW alters the row that will be inserted or updated. Thus, if the trigger function wants the triggering action to succeed normally without altering the row value,NEW (or a value equal thereto) has to be returned. To alter the row to be stored, it is possible to replace single values directly inNEW and return the modifiedNEW, or to build a complete new record/row to return. In the case of a before-trigger onDELETE, the returned value has no direct effect, but it has to be nonnull to allow the trigger action to proceed. Note thatNEW is null inDELETE triggers, so returning that is usually not sensible. The usual idiom inDELETE triggers is to returnOLD.

INSTEAD OF triggers (which are always row-level triggers, and may only be used on views) can return null to signal that they did not perform any updates, and that the rest of the operation for this row should be skipped (i.e., subsequent triggers are not fired, and the row is not counted in the rows-affected status for the surroundingINSERT/UPDATE/DELETE). Otherwise a nonnull value should be returned, to signal that the trigger performed the requested operation. ForINSERT andUPDATE operations, the return value should beNEW, which the trigger function may modify to supportINSERT RETURNING andUPDATE RETURNING (this will also affect the row value passed to any subsequent triggers, or passed to a specialEXCLUDED alias reference within anINSERT statement with anON CONFLICT DO UPDATE clause). ForDELETE operations, the return value should beOLD.

The return value of a row-level trigger firedAFTER or a statement-level trigger firedBEFORE orAFTER is always ignored; it might as well be null. However, any of these types of triggers might still abort the entire operation by raising an error.

Example 40.3 shows an example of a trigger procedure inPL/pgSQL.

Example 40.3. APL/pgSQL Trigger Procedure

This example trigger ensures that any time a row is inserted or updated in the table, the current user name and time are stamped into the row. And it checks that an employee's name is given and that the salary is a positive value.

CREATE TABLE emp (    empname text,    salary integer,    last_date timestamp,    last_user text);CREATE FUNCTION emp_stamp() RETURNS trigger AS $emp_stamp$    BEGIN        -- Check that empname and salary are given        IF NEW.empname IS NULL THEN            RAISE EXCEPTION 'empname cannot be null';        END IF;        IF NEW.salary IS NULL THEN            RAISE EXCEPTION '% cannot have null salary', NEW.empname;        END IF;        -- Who works for us when she must pay for it?        IF NEW.salary < 0 THEN            RAISE EXCEPTION '% cannot have a negative salary', NEW.empname;        END IF;        -- Remember who changed the payroll when        NEW.last_date := current_timestamp;        NEW.last_user := current_user;        RETURN NEW;    END;$emp_stamp$ LANGUAGE plpgsql;CREATE TRIGGER emp_stamp BEFORE INSERT OR UPDATE ON emp    FOR EACH ROW EXECUTE PROCEDURE emp_stamp();

Another way to log changes to a table involves creating a new table that holds a row for each insert, update, or delete that occurs. This approach can be thought of as auditing changes to a table.Example 40.4 shows an example of an audit trigger procedure inPL/pgSQL.

Example 40.4. APL/pgSQL Trigger Procedure For Auditing

This example trigger ensures that any insert, update or delete of a row in theemp table is recorded (i.e., audited) in theemp_audit table. The current time and user name are stamped into the row, together with the type of operation performed on it.

CREATE TABLE emp (    empname           text NOT NULL,    salary            integer);CREATE TABLE emp_audit(    operation         char(1)   NOT NULL,    stamp             timestamp NOT NULL,    userid            text      NOT NULL,    empname           text      NOT NULL,    salary integer);CREATE OR REPLACE FUNCTION process_emp_audit() RETURNS TRIGGER AS $emp_audit$    BEGIN        --        -- Create a row in emp_audit to reflect the operation performed on emp,        -- make use of the special variable TG_OP to work out the operation.        --        IF (TG_OP = 'DELETE') THEN            INSERT INTO emp_audit SELECT 'D', now(), user, OLD.*;            RETURN OLD;        ELSIF (TG_OP = 'UPDATE') THEN            INSERT INTO emp_audit SELECT 'U', now(), user, NEW.*;            RETURN NEW;        ELSIF (TG_OP = 'INSERT') THEN            INSERT INTO emp_audit SELECT 'I', now(), user, NEW.*;            RETURN NEW;        END IF;        RETURN NULL; -- result is ignored since this is an AFTER trigger    END;$emp_audit$ LANGUAGE plpgsql;CREATE TRIGGER emp_auditAFTER INSERT OR UPDATE OR DELETE ON emp    FOR EACH ROW EXECUTE PROCEDURE process_emp_audit();

A variation of the previous example uses a view joining the main table to the audit table, to show when each entry was last modified. This approach still records the full audit trail of changes to the table, but also presents a simplified view of the audit trail, showing just the last modified timestamp derived from the audit trail for each entry.Example 40.5 shows an example of an audit trigger on a view inPL/pgSQL.

Example 40.5. APL/pgSQL View Trigger Procedure For Auditing

This example uses a trigger on the view to make it updatable, and ensure that any insert, update or delete of a row in the view is recorded (i.e., audited) in theemp_audit table. The current time and user name are recorded, together with the type of operation performed, and the view displays the last modified time of each row.

CREATE TABLE emp (    empname           text PRIMARY KEY,    salary            integer);CREATE TABLE emp_audit(    operation         char(1)   NOT NULL,    userid            text      NOT NULL,    empname           text      NOT NULL,    salary            integer,    stamp             timestamp NOT NULL);CREATE VIEW emp_view AS    SELECT e.empname,           e.salary,           max(ea.stamp) AS last_updated      FROM emp e      LEFT JOIN emp_audit ea ON ea.empname = e.empname     GROUP BY 1, 2;CREATE OR REPLACE FUNCTION update_emp_view() RETURNS TRIGGER AS $$    BEGIN        --        -- Perform the required operation on emp, and create a row in emp_audit        -- to reflect the change made to emp.        --        IF (TG_OP = 'DELETE') THEN            DELETE FROM emp WHERE empname = OLD.empname;            IF NOT FOUND THEN RETURN NULL; END IF;            OLD.last_updated = now();            INSERT INTO emp_audit VALUES('D', user, OLD.*);            RETURN OLD;        ELSIF (TG_OP = 'UPDATE') THEN            UPDATE emp SET salary = NEW.salary WHERE empname = OLD.empname;            IF NOT FOUND THEN RETURN NULL; END IF;            NEW.last_updated = now();            INSERT INTO emp_audit VALUES('U', user, NEW.*);            RETURN NEW;        ELSIF (TG_OP = 'INSERT') THEN            INSERT INTO emp VALUES(NEW.empname, NEW.salary);            NEW.last_updated = now();            INSERT INTO emp_audit VALUES('I', user, NEW.*);            RETURN NEW;        END IF;    END;$$ LANGUAGE plpgsql;CREATE TRIGGER emp_auditINSTEAD OF INSERT OR UPDATE OR DELETE ON emp_view    FOR EACH ROW EXECUTE PROCEDURE update_emp_view();

One use of triggers is to maintain a summary table of another table. The resulting summary can be used in place of the original table for certain queries — often with vastly reduced run times. This technique is commonly used in Data Warehousing, where the tables of measured or observed data (called fact tables) might be extremely large.Example 40.6 shows an example of a trigger procedure inPL/pgSQL that maintains a summary table for a fact table in a data warehouse.

Example 40.6. APL/pgSQL Trigger Procedure For Maintaining A Summary Table

The schema detailed here is partly based on theGrocery Store example fromThe Data Warehouse Toolkit by Ralph Kimball.

---- Main tables - time dimension and sales fact.--CREATE TABLE time_dimension (    time_key                    integer NOT NULL,    day_of_week                 integer NOT NULL,    day_of_month                integer NOT NULL,    month                       integer NOT NULL,    quarter                     integer NOT NULL,    year                        integer NOT NULL);CREATE UNIQUE INDEX time_dimension_key ON time_dimension(time_key);CREATE TABLE sales_fact (    time_key                    integer NOT NULL,    product_key                 integer NOT NULL,    store_key                   integer NOT NULL,    amount_sold                 numeric(12,2) NOT NULL,    units_sold                  integer NOT NULL,    amount_cost                 numeric(12,2) NOT NULL);CREATE INDEX sales_fact_time ON sales_fact(time_key);---- Summary table - sales by time.--CREATE TABLE sales_summary_bytime (    time_key                    integer NOT NULL,    amount_sold                 numeric(15,2) NOT NULL,    units_sold                  numeric(12) NOT NULL,    amount_cost                 numeric(15,2) NOT NULL);CREATE UNIQUE INDEX sales_summary_bytime_key ON sales_summary_bytime(time_key);---- Function and trigger to amend summarized column(s) on UPDATE, INSERT, DELETE.--CREATE OR REPLACE FUNCTION maint_sales_summary_bytime() RETURNS TRIGGERAS $maint_sales_summary_bytime$    DECLARE        delta_time_key          integer;        delta_amount_sold       numeric(15,2);        delta_units_sold        numeric(12);        delta_amount_cost       numeric(15,2);    BEGIN        -- Work out the increment/decrement amount(s).        IF (TG_OP = 'DELETE') THEN            delta_time_key = OLD.time_key;            delta_amount_sold = -1 * OLD.amount_sold;            delta_units_sold = -1 * OLD.units_sold;            delta_amount_cost = -1 * OLD.amount_cost;        ELSIF (TG_OP = 'UPDATE') THEN            -- forbid updates that change the time_key -            -- (probably not too onerous, as DELETE + INSERT is how most            -- changes will be made).            IF ( OLD.time_key != NEW.time_key) THEN                RAISE EXCEPTION 'Update of time_key : % -> % not allowed',                                                      OLD.time_key, NEW.time_key;            END IF;            delta_time_key = OLD.time_key;            delta_amount_sold = NEW.amount_sold - OLD.amount_sold;            delta_units_sold = NEW.units_sold - OLD.units_sold;            delta_amount_cost = NEW.amount_cost - OLD.amount_cost;        ELSIF (TG_OP = 'INSERT') THEN            delta_time_key = NEW.time_key;            delta_amount_sold = NEW.amount_sold;            delta_units_sold = NEW.units_sold;            delta_amount_cost = NEW.amount_cost;        END IF;        -- Insert or update the summary row with the new values.        <<insert_update>>        LOOP            UPDATE sales_summary_bytime                SET amount_sold = amount_sold + delta_amount_sold,                    units_sold = units_sold + delta_units_sold,                    amount_cost = amount_cost + delta_amount_cost                WHERE time_key = delta_time_key;            EXIT insert_update WHEN found;            BEGIN                INSERT INTO sales_summary_bytime (                            time_key,                            amount_sold,                            units_sold,                            amount_cost)                    VALUES (                            delta_time_key,                            delta_amount_sold,                            delta_units_sold,                            delta_amount_cost                           );                EXIT insert_update;            EXCEPTION                WHEN UNIQUE_VIOLATION THEN                    -- do nothing            END;        END LOOP insert_update;        RETURN NULL;    END;$maint_sales_summary_bytime$ LANGUAGE plpgsql;CREATE TRIGGER maint_sales_summary_bytimeAFTER INSERT OR UPDATE OR DELETE ON sales_fact    FOR EACH ROW EXECUTE PROCEDURE maint_sales_summary_bytime();INSERT INTO sales_fact VALUES(1,1,1,10,3,15);INSERT INTO sales_fact VALUES(1,2,1,20,5,35);INSERT INTO sales_fact VALUES(2,2,1,40,15,135);INSERT INTO sales_fact VALUES(2,3,1,10,1,13);SELECT * FROM sales_summary_bytime;DELETE FROM sales_fact WHERE product_key = 1;SELECT * FROM sales_summary_bytime;UPDATE sales_fact SET units_sold = units_sold * 2;SELECT * FROM sales_summary_bytime;

40.9.2. Triggers on Events

PL/pgSQL can be used to define event triggers.Postgres Pro requires that a procedure that is to be called as an event trigger must be declared as a function with no arguments and a return type ofevent_trigger.

When aPL/pgSQL function is called as an event trigger, several special variables are created automatically in the top-level block. They are:

TG_EVENT

Data typetext; a string representing the event the trigger is fired for.

TG_TAG

Data typetext; variable that contains the command tag for which the trigger is fired.

Example 40.7 shows an example of an event trigger procedure inPL/pgSQL.

Example 40.7. APL/pgSQL Event Trigger Procedure

This example trigger simply raises aNOTICE message each time a supported command is executed.

CREATE OR REPLACE FUNCTION snitch() RETURNS event_trigger AS $$BEGIN    RAISE NOTICE 'snitch: % %', tg_event, tg_tag;END;$$ LANGUAGE plpgsql;CREATE EVENT TRIGGER snitch ON ddl_command_start EXECUTE PROCEDURE snitch();


Prev Up Next
40.8. Errors and Messages Home 40.10. PL/pgSQL Under the Hood
pdfepub
Go to Postgres Pro Standard 9.5
By continuing to browse this website, you agree to the use of cookies. Go toPrivacy Policy.

[8]ページ先頭

©2009-2025 Movatter.jp