Re: minimal update

From: Kenneth Marshall <ktm(at)rice(dot)edu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Simon Riggs <simon(at)2ndQuadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>, Michael Glaesemann <grzm(at)seespotcode(dot)net>, David Fetter <david(at)fetter(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: minimal update
Date: 2008-10-22 22:10:55
Message-ID: 20081022221055.GS27578@it.is.rice.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Oct 22, 2008 at 06:05:26PM -0400, Tom Lane wrote:
> Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> >> On Wed, Oct 22, 2008 at 3:24 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >>> "Minimal" really fails to convey the point here IMHO. 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.
>
> Agreed --- I was hoping someone could improve on that part. The only
> other words I could come up with were "empty" and "useless", neither of
> which seem quite le mot juste ...
>
> regards, tom lane
>
redundant?

Ken

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2008-10-22 22:11:50 Re: minimal update
Previous Message Tom Lane 2008-10-22 22:05:26 Re: minimal update