| From: | "Robert Haas" <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "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:57:19 |
| Message-ID: | 603c8f070810221557g17a0ef94p627b4b39355d186f@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> How about one of these?:
> suppress_same_value_updates_trigger
> suppress_no_change_updates_trigger
> suppress_no_effect_updates_trigger
I like the first one. A trigger firing would be an "effect", and
possibly a "change", but "same value" seems very clear.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-10-22 23:03:48 | Re: psql Feature request \set query |
| Previous Message | Tom Lane | 2008-10-22 22:53:29 | Re: Re: [COMMITTERS] pgsql: Rework subtransaction commit protocol for hot standby. |