Re: minimal update

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Simon Riggs" <simon(at)2ndQuadrant(dot)com>, "Robert Haas" <robertmhaas(at)gmail(dot)com>
Cc: "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "David Fetter" <david(at)fetter(dot)org>, "Gurjeet Singh" <singh(dot)gurjeet(at)gmail(dot)com>, "Magnus Hagander" <magnus(at)hagander(dot)net>, "Bruce Momjian" <bruce(at)momjian(dot)us>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>, "Michael Glaesemann" <grzm(at)seespotcode(dot)net>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: minimal update
Date: 2008-10-22 22:11:50
Message-ID: 48FF5ED6.EE98.0025.0@wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>>> Simon Riggs <simon(at)2ndQuadrant(dot)com> wrote:
>> On Wed, Oct 22, 2008 at 3:24 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2008-10-22 22:20:44 Re: Block level concurrency during recovery
Previous Message Kenneth Marshall 2008-10-22 22:10:55 Re: minimal update