| From: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
|---|---|
| To: | Michael Lewis <mlewis(at)entrata(dot)com> |
| Cc: | Mitar <mmitar(at)gmail(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Determining if a table really changed in a trigger |
| Date: | 2021-10-26 23:16:45 |
| Message-ID: | E836C919-AD39-47DA-BEA3-8B6D0C9F34A8@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On Oct 26, 2021, at 4:01 PM, Michael Lewis <mlewis(at)entrata(dot)com> wrote:
>
> Does this perform differently from suppress_redundant_updates_trigger?
>
> https://www.postgresql.org/docs/current/functions-trigger.html
If Mitar finds that suppress_redundant_updates_trigger is sufficient, that may be a simpler solution. Thanks for mentioning it.
The suppress_redundant_updates_trigger uses memcmp on the old and new rows. I don't know if memcmp will be sufficient in this case, since json can be binary unequal and yet turn out to be equal once cast to jsonb. I was using the rule and casting the json column to jsonb before comparing for equality.
—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Lewis | 2021-10-26 23:32:24 | Re: How to copy rows into same table efficiently |
| Previous Message | Michael Lewis | 2021-10-26 23:01:01 | Re: Determining if a table really changed in a trigger |