[GENERAL] UPDATE column without FK fires other FK triggers constraint check - Mailing list pgsql-general

From Luca Looz
Subject [GENERAL] UPDATE column without FK fires other FK triggers constraint check
Date
Msg-id CAHXaXTw_2va3Dk9oT0KpEq9-t-c1MMAm0YOLhtU6ER4M31+wSw@mail.gmail.com
Whole thread Raw
Responses Re: [GENERAL] UPDATE column without FK fires other FK triggers constraint check
List pgsql-general
I was analyzing an update function and i have noticed "Trigger for constraint" entries for foreign keys that i wasn't using or referring.
After some tests it seems that this happens when the same row is covered by more than 1 update in the same transaction even without any change.

Here is a dbfiddle example:

Is this an expected behavior? Why it happens?

I have initially asked this on dba stackexchange:

pgsql-general by date:

Previous
From: basti
Date:
Subject: Re: [GENERAL] log_filename
Next
From: Mikhail
Date:
Subject: [GENERAL] Index Only Scan and Heap Fetches