Re: minimal update

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 21:56:37
Message-ID: 1224712597.27145.528.camel@ebony.2ndQuadrant
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On Wed, 2008-10-22 at 17:24 -0400, Robert Haas wrote:
> On Wed, Oct 22, 2008 at 3:24 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> >> Can we call the function "minimal_update_trigger", rather than min_...
> >
> > "Minimal" really fails to convey the point here IMHO. How about
> > something like "suppress_no_op_updates_trigger"?
>
> +1. That's a much better name.
>

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.

--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-10-22 22:05:26 Re: minimal update
Previous Message Emmanuel Cecchet 2008-10-22 21:49:53 Re: Fwd: [PATCHES] Auto Partitioning Patch - WIP version 1