Re: Command Triggers, patch v11 - Mailing list pgsql-hackers

From Thom Brown
Subject Re: Command Triggers, patch v11
Date
Msg-id CAA-aLv4h-BJTwxq6pSKwJQ8pij4uPcKzJKrckegemfUGHR++hQ@mail.gmail.com
Whole thread Raw
In response to Re: Command Triggers, patch v11  (Thom Brown <thom@linux.com>)
List pgsql-hackers
On 9 March 2012 00:28, Thom Brown <thom@linux.com> wrote:
> On 8 March 2012 22:24, Dimitri Fontaine <dimitri@2ndquadrant.fr> wrote:
>
> We're getting there. :)

It was late last night and I forgot to get around to testing pg_dump,
which isn't working correctly:


--
-- Name: cmd_trg_after_alter_aggregate; Type: COMMAND TRIGGER; Schema:
-; Owner:
--

CREATE COMMAND TRIGGER cmd_trg_after_alter_aggregate AFTER"ALTER
AGGREGATE" EXECUTE PROCEDURE cmd_trg_info ();


There shouldn't be quotes around the command, and when removing them,
ensure there's a space before the command.  All variations of the
ALTER statements in the dump are fine, so are CREATE statements for
ANY COMMAND command triggers.

Also I notice that CREATE/ALTER/DROP COMMAND TRIGGER appears just
before CREATE/ALTER/DROP TRIGGER in the documentation.  This breaks
the alphabetical order and I wasn't expecting to find it there when
scanning down the page.  Could we move them into an alphabetic
position?

-- 
Thom


pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Bug: walsender and high CPU usage
Next
From: Fujii Masao
Date:
Subject: Re: xlog location arithmetic