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

Re: Use of systable_beginscan_ordered in event trigger patch

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Use of systable_beginscan_ordered in event trigger patch
Date: 2012-08-28 17:37:50
Message-ID: CA+TgmoZR3H6fBFkt2AoueCRTPfVzVf853++pGk=xB4bPPzaCiA@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Tue, Aug 28, 2012 at 12:47 PM, Andres Freund <andres(at)2ndquadrant(dot)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


In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2012-08-28 17:39:42
Subject: Re: MySQL search query is not executing in Postgres DB
Previous:From: Robert HaasDate: 2012-08-28 17:32:51
Subject: Re: MySQL search query is not executing in Postgres DB

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