Re: [HACKERS] delta relations in AFTER triggers - Mailing list pgsql-hackers

From Corey Huinker
Subject Re: [HACKERS] delta relations in AFTER triggers
Date
Msg-id CADkLM=fPJnuZNVQWy1YygZ5=PeuamAvrrDqF3XGW2+=BdRBUiw@mail.gmail.com
Whole thread Raw
In response to Re: delta relations in AFTER triggers  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [HACKERS] delta relations in AFTER triggers  (Prabhat Sahu <prabhat.sahu@enterprisedb.com>)
List pgsql-hackers
Great.  Thanks.  I wonder if there is some way we can automatically
include code fragments in the documentation without keeping them in
sync manually.


In whatever extra docs you add, could you include an example of an INSERT ON CONFLICT, and potentially a CTE query that does two operations on the same table. I'm not clear on what to expect when a statement does a mix of INSERT, UPDATE, and DELETE? Will there be multiple firings of the trigger in a single statement, or will the before/after sets be mashed together regardless of which part of the query generated it?

 

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] pg_upgrade vs extension upgrades
Next
From: Euler Taveira
Date:
Subject: [HACKERS] Different table schema in logical replication crashes