Re: minimal update - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: minimal update
Date
Msg-id 48FF5ED6.EE98.0025.0@wicourts.gov
Whole thread Raw
In response to Re: minimal update  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: minimal update
List pgsql-hackers
>>> Simon Riggs <simon@2ndQuadrant.com> wrote: 
>> On Wed, Oct 22, 2008 at 3:24 PM, Tom Lane <tgl@sss.pgh.pa.us>
wrote:
>> > How about
>> > something like "suppress_no_op_updates_trigger"?
> 
> I think it means something to us, but "no op" is a very technical
phrase
> that probably doesn't travel very well. Not everybody Majored in
Comp
> Sci and speaks Amglish as their native language.
> 
> Certainly this intention is much better than "minimal", but a more
> widely acceptable phrase is probably better. I will avoid trying to
come
> up with something myself though.
How about one of these?: suppress_same_value_updates_trigger suppress_no_change_updates_trigger
suppress_no_effect_updates_trigger
They all seem a bit awkward, but the best that came to mind.
-Kevin


pgsql-hackers by date:

Previous
From: Kenneth Marshall
Date:
Subject: Re: minimal update
Next
From: Simon Riggs
Date:
Subject: Re: Block level concurrency during recovery