Re: Not using suppress_redundant_updates_trigger in sql-createtrigger.html#examples

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: petermpallesen(at)gmail(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: Not using suppress_redundant_updates_trigger in sql-createtrigger.html#examples
Date: 2020-06-16 17:39:45
Message-ID: 1369890.1592329185@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> I have developed the attached patch which is in a better direction.

I still wish you wouldn't jam this topic into an only-marginally-related
sentence. In the case at hand, the point that the existing text is
making is that a no-op update will fire triggers. Which is not
something that suppress_redundant_updates_trigger will suppress,
so again it seems confusing to mention that in the same breath.

I think that perhaps the right thing to do is add a new para to
CREATE TRIGGER's "Notes" section, along the lines of

There are a few built-in trigger functions that can be used
to solve common problems without having to write your own trigger
code. See Section 9.28.

This would have the advantage of covering the other built-in triggers
not only suppress_redundant_updates_trigger.

regards, tom lane

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Bruce Momjian 2020-06-16 17:49:04 Re: Not using suppress_redundant_updates_trigger in sql-createtrigger.html#examples
Previous Message Bruce Momjian 2020-06-16 16:41:08 Re: Not using suppress_redundant_updates_trigger in sql-createtrigger.html#examples