Re: Use of systable_beginscan_ordered in event trigger patch - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Use of systable_beginscan_ordered in event trigger patch
Date
Msg-id CA+TgmoZR3H6fBFkt2AoueCRTPfVzVf853++pGk=xB4bPPzaCiA@mail.gmail.com
Whole thread Raw
In response to Re: Use of systable_beginscan_ordered in event trigger patch  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
On Tue, Aug 28, 2012 at 12:47 PM, Andres Freund <andres@2ndquadrant.com> wrote:
> On Tuesday, August 28, 2012 06:39:50 PM Tom Lane wrote:
>> Or maybe we should disable event triggers altogether in standalone mode?
>> I can think of plenty of ways that a broken event trigger could cause
>> enough havoc that you'd wish there was a way to suppress it, at least
>> for long enough to drop it again.
> +1

+1.  I initially suggested a PGC_SUSET GUC to disable event triggers,
and I'm still not entirely convinced that we shouldn't have one.
Maybe we could just force it to disabled in standalone mode.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: MySQL search query is not executing in Postgres DB
Next
From: Tom Lane
Date:
Subject: Re: MySQL search query is not executing in Postgres DB