Re: minimal update

From: "Merlin Moncure" <mmoncure(at)gmail(dot)com>
To: "Magnus Hagander" <magnus(at)hagander(dot)net>
Cc: "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "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-21 13:39:09
Message-ID: b42b73150810210639k255559dek93675d852ec3da09@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Oct 21, 2008 at 9:34 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> On 20 okt 2008, at 16.51, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>>
>> No, it's not just a hack. It's very close to what we'd probably do if we
>> built the facility right into the language, although it does involve the
>> overhead of calling the trigger. However, it performs reasonably well - not
>> surprising since the guts of it is just a memcmp() call.
>>
> In that case, why not put the trigger in core so people can use it easily?

+1

This is hard to get right and a common source of errors.

merlin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-10-21 13:40:56 Re: minimal update
Previous Message David Fetter 2008-10-21 13:36:30 Re: minimal update