Re: naming triggers for execution - Mailing list pgsql-general

From srkrishna@myself.com
Subject Re: naming triggers for execution
Date
Msg-id trinity-301b95ac-bff7-4d5b-b0d1-2ee05781021e-1573830063667@3c-app-mailcom-lxa12
Whole thread Raw
In response to naming triggers for execution  (PegoraroF10 <marcos@f10.com.br>)
Responses Re: naming triggers for execution  (PegoraroF10 <marcos@f10.com.br>)
List pgsql-general

> But suppose we have two triggers, one is called for every table for auditing
> purposes, for example. And other for a specific process of that table.
> Considering that the auditing needs to be the last, how can I be sure it´ll
> ran lastly ?
 
 
May be I am not getting the full picture.  Why can't you name the audit table trigger as Z* 
to make it the last one to be executed.



pgsql-general by date:

Previous
From: Ivan Sergio Borgonovo
Date:
Subject: porting horde to Postgresql 12, dropped pg_attrdef
Next
From: github kran
Date:
Subject: Re: PostGreSQL Replication and question on maintenance