Re: Command Triggers, v16 - Mailing list pgsql-hackers

From Dimitri Fontaine
Subject Re: Command Triggers, v16
Date
Msg-id m2aa3hle5i.fsf@2ndQuadrant.fr
Whole thread Raw
In response to Re: Command Triggers, v16  (Thom Brown <thombrown@gmail.com>)
Responses Re: Command Triggers, v16
Re: Command Triggers, v16
Re: Command Triggers, v16
List pgsql-hackers
Thanks for testing this new version (again).

A quick answer now, I'll send another patch tomorrow.

Thom Brown <thombrown@gmail.com> writes:
> I don’t understand how functions can return a type of “command
> trigger”.  This certainly works, but I’ve never seen a type consisting
> of more than one word.  Could you explain this for me?  This is also

I tricked that in the grammar, the type is called cmdtrigger but I
though it wouldn't be a good choice for the SQL statement.

> at odds with the error message in src/backend/commands/cmdtrigger.c:
>
> errmsg("function \"%s\" must return type \"trigger\"",

I realized I needed another trigger like data type after I had worked
this message, I need to get back on it, thanks.

> At this moment in time, CTAS is still outstanding.  Is the plan to try
> to get that in for this release, or as an enhancement in 9.3?

The plan is to get CTAS as a utility command in 9.2 then update the
command trigger patch to benefit from the new situation. We've been
wondering about making its own commit fest entry for that patch, it's
now clear in my mind, that needs to happen.

Stay tuned, follow up email due tomorrow.
--
Dimitri Fontaine
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: foreign key locks, 2nd attempt
Next
From: Simon Riggs
Date:
Subject: Re: foreign key locks, 2nd attempt