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.

diff --git a/contrib/bdr/bdr--0.5.sql b/contrib/bdr/bdr--0.5.sql
index f5ba5303eecd1aa1943d49f4550e54b89fb949c2..f6554b614eb641b040077ffdbb4cb4327ba0391f 100644 (file)
--- 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()';