Re: Determining if a table really changed in a trigger
От | Mark Dilger |
---|---|
Тема | Re: Determining if a table really changed in a trigger |
Дата | |
Msg-id | E836C919-AD39-47DA-BEA3-8B6D0C9F34A8@enterprisedb.com обсуждение исходный текст |
Ответ на | Re: Determining if a table really changed in a trigger (Michael Lewis <mlewis@entrata.com>) |
Ответы |
Re: Determining if a table really changed in a trigger
|
Список | pgsql-general |
> On Oct 26, 2021, at 4:01 PM, Michael Lewis <mlewis@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 mentioningit. The suppress_redundant_updates_trigger uses memcmp on the old and new rows. I don't know if memcmp will be sufficient inthis case, since json can be binary unequal and yet turn out to be equal once cast to jsonb. I was using the rule andcasting the json column to jsonb before comparing for equality. — Mark Dilger EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-general по дате отправления: