| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-08-28 17:39:42 | Re: MySQL search query is not executing in Postgres DB |
| Previous Message | Robert Haas | 2012-08-28 17:32:51 | Re: MySQL search query is not executing in Postgres DB |