From cd3413ec3683918c9cb9cfb39ae5b2c32f231e8b Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Tue, 11 Dec 2012 19:28:31 -0500 Subject: Disable event triggers in standalone mode. Per discussion, this seems necessary to allow recovery from broken event triggers, or broken indexes on pg_event_trigger. Dimitri Fontaine --- doc/src/sgml/ref/create_event_trigger.sgml | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/ref/create_event_trigger.sgml b/doc/src/sgml/ref/create_event_trigger.sgml index 08894b22cfb..040df118153 100644 --- a/doc/src/sgml/ref/create_event_trigger.sgml +++ b/doc/src/sgml/ref/create_event_trigger.sgml @@ -108,7 +108,14 @@ CREATE EVENT TRIGGER name Notes - To create a trigger on a event, the user must be superuser. + Only superusers can create event triggers. + + + + Event triggers are disabled in single-user mode (see ). If an erroneous event trigger disables the + database so much that you can't even drop the trigger, restart in + single-user mode and you'll be able to do that. @@ -116,7 +123,7 @@ CREATE EVENT TRIGGER name Examples - Forbid the execution of any ddl command: + Forbid the execution of any DDL command: CREATE OR REPLACE FUNCTION abort_any_command() -- cgit v1.2.3