| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: triggered_change_notification v3 |
| Date: | 2012-01-20 04:16:10 |
| Message-ID: | CA+TgmoY6t1vKLzSHn7Ls8VzmYJTdG8Axq2-EhUW002uXWK1GtA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Jan 15, 2012 at 11:05 PM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> Attached is a version of a previously posted patch which has been
> modified based on on-list feedback from Álvaro.
>
> This is a generalized trigger function which can be used as an AFTER
> EACH ROW trigger on any table which has a primary key, and will send
> notifications of operations for which the trigger is attached, with a
> payload indicating the table, the operation, and the primary key. A
> channel can be specified in the CREATE TRIGGER command, but will
> default to "tcn" if omitted.
Nice work, Kevin. I've committed this.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2012-01-20 04:29:03 | Re: Vacuum rate limit in KBps |
| Previous Message | Steve Singer | 2012-01-20 04:01:49 | Re: Online base backup from the hot-standby |