From faf42d917865698f0a3d149db59dd9b17b8d2823 Mon Sep 17 00:00:00 2001 From: Alvaro Herrera Date: Tue, 29 Apr 2014 14:07:04 -0400 Subject: [PATCH] bdr/deparse: don't use TG_TAG It's not useful in case of nested commands (maybe in other cases too); rely on pg_event_trigger_get_creation_commands().command_tag instead. --- contrib/bdr/bdr--0.5.sql | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contrib/bdr/bdr--0.5.sql b/contrib/bdr/bdr--0.5.sql index f5ba5303ee..f6554b614e 100644 --- a/contrib/bdr/bdr--0.5.sql +++ b/contrib/bdr/bdr--0.5.sql @@ -211,7 +211,7 @@ BEGIN pg_catalog.pg_event_trigger_expand_command(r.command), 'false'); - IF TG_TAG = 'CREATE TABLE' and r.object_type = 'table' THEN + IF r.command_tag = 'CREATE TABLE' and r.object_type = 'table' THEN EXECUTE 'CREATE TRIGGER truncate_trigger AFTER TRUNCATE ON ' || r.identity || ' FOR EACH STATEMENT EXECUTE PROCEDURE bdr.queue_truncate()'; -- 2.39.5