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

From Robert Haas
Subject Re: Command Triggers, v16
Date
Msg-id CA+TgmoZZ9Rqf4_QJ3MGpFFB0FvypnCGoj7nUZ5cBozFHgCoGoQ@mail.gmail.com
Whole thread Raw
In response to Re: Command Triggers, v16  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
List pgsql-hackers
On Mon, Mar 26, 2012 at 3:24 PM, Dimitri Fontaine
<dimitri@2ndquadrant.fr> wrote:
> One use case would be for londiste/slony/bucardo to rewrite the command
> and queue its text, that will be done in C and should probably be done
> first. Using an ANY command trigger means that code will run before user
> specific code (or likewise after it).

And, if the user wants it to be run first, he or she can do that.  But
suppose he wants to run it first, and also forbid users whose username
starts with the letter b from running the ANALYZE command.  Well,
then, he now wants that trigger to come before the other one, even
though the Slony trigger is for all commands (maybe) and the other
just for ANALYZE (maybe).

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Remove dead assignment
Next
From: Tom Lane
Date:
Subject: Re: Command Triggers, v16