Re: minimal update - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: minimal update
Date
Msg-id 48FC9B0A.4000502@dunslane.net
Whole thread Raw
In response to Re: minimal update  (Magnus Hagander <magnus@hagander.net>)
Responses Re: minimal update
List pgsql-hackers

Magnus Hagander wrote:
> Andrew Dunstan wrote:
>   
>> Tom Lane wrote:
>>     
>>> Andrew Dunstan <andrew@dunslane.net> writes:
>>>  
>>>       
>>>> OK. Where would be a good place to put the code? Maybe a new file
>>>> src/backend/utils/adt/trigger_utils.c ?
>>>>     
>>>>         
>>> I thought the plan was to make it a contrib module.
>>>
>>>            
>>>   
>>>       
>> Well, previous discussion did mention catalog entries, which would
>> suggest otherwise, but I can do it as a contrib module if that's the
>> consensus.
>>     
>
> What would be the actual reason to put it in contrib and not core? Are
> there any "dangers" by having it there? Or is it "just a hack" and not a
> "real solution"?
>
>
>   

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.

cheers

andrew


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Window Functions: buffering strategy
Next
From: Simon Riggs
Date:
Subject: Re: Block level concurrency during recovery