| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Euler Taveira <euler(at)eulerto(dot)com>, Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>, Daniel Gustafsson <daniel(at)yesql(dot)se>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Trigger position |
| Date: | 2021-09-15 15:30:42 |
| Message-ID: | 202109151530.sdgdd7k4tode@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2021-Sep-15, Pavel Stehule wrote:
> Triggers that depend on execution order are pretty hell. It is a clean
> signal of some crazy design and overusing of triggers.
Yeah. The only case I've seen where order of triggers was important
(beyond the "before" / "after" classification) is where you have
something that you need to ensure runs before the FK triggers.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"XML!" Exclaimed C++. "What are you doing here? You're not a programming
language."
"Tell that to the people who use me," said XML.
https://burningbird.net/the-parable-of-the-languages/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chapman Flack | 2021-09-15 15:31:16 | Re: Trigger position |
| Previous Message | Tom Lane | 2021-09-15 15:28:28 | Re: EXPLAIN(VERBOSE) to CTE with SEARCH BREADTH FIRST fails |