Not using suppress_redundant_updates_trigger in sql-createtrigger.html#examples
От | PG Doc comments form |
---|---|
Тема | Not using suppress_redundant_updates_trigger in sql-createtrigger.html#examples |
Дата | |
Msg-id | 159195294959.673.5752624528747900508@wrigleys.postgresql.org обсуждение исходный текст |
Ответы |
Re: Not using suppress_redundant_updates_trigger insql-createtrigger.html#examples
|
Список | pgsql-docs |
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/12/bug-reporting.html Description: Hi I was stumbling across the trigger function ‘suppress_redundant_updates_trigger’ in https://www.postgresql.org/docs/devel/functions-trigger.html and I would just ask if there is any reason of this not being int the documentation in https://www.postgresql.org/docs/13/sql-createtrigger.html. So after Call a function to log updates of accounts, but only if something changed: CREATE TRIGGER log_update AFTER UPDATE ON accounts FOR EACH ROW WHEN (OLD.* IS DISTINCT FROM NEW.*) EXECUTE FUNCTION log_account_update(); There could be an alternative implementation as well CREATE TRIGGER log_update AFTER UPDATE ON accounts FOR EACH ROW EXECUTE FUNCTION log_account_update(); CREATE TRIGGER suppress_redundant_account_after_updates AFTER UPDATE ON accounts FOR EACH ROW EXECUTE FUNCTION suppress_redundant_updates_trigger(); Just to introduce and like the feature. Thank you for your great work best regards
В списке pgsql-docs по дате отправления: