| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org, Thom Brown <thombrown(at)gmail(dot)com> |
| Subject: | Re: Command Triggers, v16 |
| Date: | 2012-03-26 20:05:42 |
| Message-ID: | CA+TgmoZZ9Rqf4_QJ3MGpFFB0FvypnCGoj7nUZ5cBozFHgCoGoQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Mar 26, 2012 at 3:24 PM, Dimitri Fontaine
<dimitri(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-03-26 20:06:36 | Re: Command Triggers, v16 |
| Previous Message | Tom Lane | 2012-03-26 19:53:52 | Re: [COMMITTERS] pgsql: Remove dead assignment |