Skip site navigation (1) Skip section navigation (2)

Re: minimal update

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Kenneth Marshall <ktm(at)rice(dot)edu>, Simon Riggs <simon(at)2ndQuadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, 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-30 03:24:07
Message-ID: 3705.1225337047@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> I think I like this best of all the suggestions - 
> suppress_redundant_updates_trigger() is what I have now.

> If there's no further discussion, I'll go ahead and commit this in a day 
> or two.

The documentation seems a bit lacking: it gives neither a hint of why
you might want to use this nor why it's not the built-in behavior.
Suggest expending a sentence or two pointing out that the trigger takes
nonzero execution time to do its comparisons, and that this may or may
not be repaid by eliminated updates, depending on whether the client
applications are actually in the habit of issuing useless update
commands.

I think you're missing an <indexentry> item for the function name, also.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2008-10-30 03:27:04
Subject: Re: pre-MED
Previous:From: Tom LaneDate: 2008-10-30 03:12:50
Subject: Re: Please make sure your patches are on the wiki page

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group