Re: ALTER TABLE ... NOREWRITE option - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: ALTER TABLE ... NOREWRITE option
Date
Msg-id CA+U5nMK7oXkZ=hicK7cqCV87uiWV8=tOinA=-hrx31XKDF6-jg@mail.gmail.com
Whole thread Raw
In response to Re: ALTER TABLE ... NOREWRITE option  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: ALTER TABLE ... NOREWRITE option  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
On 6 December 2012 00:46, Robert Haas <robertmhaas@gmail.com> wrote:
> On Wed, Dec 5, 2012 at 6:45 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
>> Yes, but it is also the trigger writers problem.
>
> Maybe to some degree.  I don't think that a server crash or something
> like a block-read error is ever tolerable though, no matter how silly
> the user is with their event trigger logic.  If we go down that road
> it will be impossible to know whether errors that are currently
> reliable indicators of software or hardware problems are in fact
> caused by event triggers.   Of course, if an event trigger causes the
> system to error out in some softer way, that's perfectly fine...

How are event triggers more dangerous than normal triggers/functions?

-- Simon Riggs                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: in-catalog Extension Scripts and Control parameters (templates?)
Next
From: Tom Lane
Date:
Subject: Re: How to check whether the row was modified by this transaction before?