Re: minimal update - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: minimal update
Date
Msg-id 472B61EB.50604@dunslane.net
Whole thread Raw
In response to Re: minimal update  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: minimal update  (Michael Glaesemann <grzm@seespotcode.net>)
List pgsql-hackers

Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
>   
>> Tom Lane wrote:
>>     
>>> A BEFORE UPDATE trigger would be better, and probably hardly more
>>> expensive than a wired-in facility (especially if you were willing to
>>> write it in C).
>>>       
>
>   
>> Yes. I also  prefer the trigger idea to a rule because triggers are easy 
>> to enable  and disable. It's still a lot of work for what must be a 
>> common want, though. Could it be done generically?
>>     
>
> Well, you could write the trigger in C and it'd work for any table.
> I think it could be as simple as a memcmp of the tuples' data areas,
> since we now require padding bytes to be 0 ...
>
>             
>   

Ah. Good. Thanks, that's the piece I was missing.

cheers

andrew


pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Test lab
Next
From: ohp@pyrenet.fr
Date:
Subject: should I worry?