[MASSMAIL]Question on trigger - Mailing list pgsql-general

From veem v
Subject [MASSMAIL]Question on trigger
Date
Msg-id CAB+=1TV2rVqySeVeviDfoKc0ApiLPQ9=i=5PM9R6ek-_aKuhOg@mail.gmail.com
Whole thread Raw
Responses Re: Question on trigger  (Adrian Klaver <adrian.klaver@aklaver.com>)
List pgsql-general
Hi, We used to use Oracle database in which we had audit triggers(something as below) mandated for all tables by the control team. Now we are going to use the postgresql 15.4 database for one of our applications. So,wanted to understand if there exists any downside of such audit trigger setup for all the tables? Will it impact the bulk data insert/update/delete OR slowdown of any of the DML operations significantly (and thus will not be advisable to use for all tables but selected ones)?

CREATE OR REPLACE TRIGGER TAB_AUD_TRG
  BEFORE DELETE OR INSERT OR UPDATE
  ON tab
  FOR EACH ROW
BEGIN
      IF inserting THEN
        :NEW.create_timestamp := systimestamp;
        :NEW.create_userid  := sys_context('USERENV','SESSION_USER');
        :NEW.update_timestamp := systimestamp;
        :NEW.update_userid := sys_context('USERENV','SESSION_USER');
      ELSIF updating THEN
        IF  updating('create_userid') OR updating('create_timestamp') THEN
            :new.create_userid   := :old.create_userid;
            :new.create_timestamp  := :old.create_timestamp;
        END IF;
        :NEW.update_timestamp := systimestamp;
        :NEW.update_userid := sys_context('USERENV','SESSION_USER');
      END IF;
  END;
/


Regards
Veem

pgsql-general by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: subquery plan rows = 1, but it's merge joined instead of index lookup
Next
From: Ilya Basin
Date:
Subject: Re: subquery plan rows = 1, but it's merge joined instead of index lookup