Search Postgresql Archives

Re: Determining if a table really changed in a trigger

Subject: Re: Determining if a table really changed in a trigger
From: Michael Lewis <mlewis@xxxxxxxxxxx>
Date: Tue, 26 Oct 2021 17:01:01 -0600
Cc: Mitar <mmitar@xxxxxxxxx>, Postgres General <pgsql-general@xxxxxxxxxxxxxx>
In-reply-to: <6526D693-D520-4B94-B44F-4A2770FBF778@enterprisedb.com>
References: <CAKLmikNjiz=zwf9suiAHoBLrRpjLTNsQ=f4PGD3RMFBxzR-3OA@mail.gmail.com> <E35E8F8C-4F85-4FFB-8A98-B1924678874E@enterprisedb.com> <CAKLmikPA6Nj65X_sbSh6XoROLuY_FeXd8AmpxuM-LWw5EnMxpQ@mail.gmail.com> <AD34DA0A-C6F4-4993-953C-36D7D973315D@enterprisedb.com> <CAKLmikMy+90f3GSqeMKsiV-qTX0Zc3VyGDCerrOJHo_usV=K4A@mail.gmail.com> <6526D693-D520-4B94-B44F-4A2770FBF778@enterprisedb.com>

Does this perform differently from suppress_redundant_updates_trigger?

Follow-Ups:
- Re: Determining if a table really changed in a trigger
  - From: Mark Dilger

References:
- Determining if a table really changed in a trigger
  - From: Mitar
- Re: Determining if a table really changed in a trigger
  - From: Mark Dilger
- Re: Determining if a table really changed in a trigger
  - From: Mitar
- Re: Determining if a table really changed in a trigger
  - From: Mark Dilger
- Re: Determining if a table really changed in a trigger
  - From: Mitar
- Re: Determining if a table really changed in a trigger
  - From: Mark Dilger