> On Oct 26, 2021, at 4:01 PM, Michael Lewis <mle...@entrata.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
- Re: Determining if a table really changed in a trigger Alban Hertroys
- Re: Determining if a table really changed in a trigge... Marcos Pegoraro
- Re: Determining if a table really changed in a tr... Alban Hertroys
- Re: Determining if a table really changed in a trigger Mitar
- Re: Determining if a table really changed in a trigger Mark Dilger
- Re: Determining if a table really changed in a trigge... Mitar
- Re: Determining if a table really changed in a tr... Mark Dilger
- Re: Determining if a table really changed in ... Mitar
- Re: Determining if a table really changed... Mark Dilger
- Re: Determining if a table really ch... Michael Lewis
- Re: Determining if a table reall... Mark Dilger
- Re: Determining if a table reall... Mitar
- Re: Determining if a table reall... Michael Lewis
- Re: Determining if a table reall... Mitar
- Re: Determining if a table really ch... Mitar
- Re: Determining if a table really changed... Marcos Pegoraro
- Re: Determining if a table really changed in a trigger Thomas Kellerer