Re: Command Triggers, patch v11

From: Thom Brown <thom(at)linux(dot)com>
To: Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>
Cc: pgsql-hackers(at)postgresql(dot)org, Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Command Triggers, patch v11
Date: 2012-03-09 11:53:38
Message-ID: CAA-aLv4h-BJTwxq6pSKwJQ8pij4uPcKzJKrckegemfUGHR++hQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 9 March 2012 00:28, Thom Brown <thom(at)linux(dot)com> wrote:
> On 8 March 2012 22:24, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2012-03-09 12:11:13 Re: xlog location arithmetic
Previous Message Fujii Masao 2012-03-09 11:40:20 Bug: walsender and high CPU usage