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

Re: minimal update

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 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-22 18:43:24
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers

Andrew Dunstan wrote:
> Tom Lane wrote:
>> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>>> In that case, why not put the trigger in core so people can use it  
>>> easily?
>> One advantage of making it a contrib module is that discussing how/when
>> to use it would fit more easily into the structure of the
>> documentation.  There is no place in our docs that a "standard trigger"
>> would fit without seeming like a wart; but a contrib module can document
>> itself pretty much however it wants.
> I was thinking a new section on 'trigger functions' of the functions 
> and operators chapter, linked from the 'create trigger' page. That 
> doesn't seem like too much of a wart.

There seems to be a preponderance of opinion for doing this as a 
builtin. Here is a patch that does it that way, along with docs and 
regression test.



Attachment: min-update.patch
Description: text/x-patch (8.9 KB)

In response to


pgsql-hackers by date

Next:From: Kevin GrittnerDate: 2008-10-22 18:56:53
Subject: Re: minimal update
Previous:From: Simon RiggsDate: 2008-10-22 18:08:52
Subject: Re: [COMMITTERS] pgsql: Rework subtransaction commit protocol forhot standby.

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