| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Greg Sabino Mullane <greg(at)turnstep(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] Cannot use all four trigger events at once |
| Date: | 2009-06-17 22:50:30 |
| Message-ID: | 5780.1245279030@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Greg Sabino Mullane <greg(at)turnstep(dot)com> writes:
> This was failing:
> CREATE TRIGGER foo
> AFTER INSERT OR UPDATE OR DELETE OR TRUNCATE
> ON foobar
> FOR EACH STATEMENT EXECUTE PROCEDURE baz();
> Turns out the parser wasn't set up to handle four different trigger
> event types.
Hmm, that's a problem ...
> Patch attached.
... but this patch doesn't come close to fixing it. struct CreateTrigStmt
needs changes. I kinda think the restriction to 4 (or whatever)
elements ought to go away altogether.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2009-06-18 00:45:45 | Re: [HACKERS] Cannot use all four trigger events at once |
| Previous Message | Greg Sabino Mullane | 2009-06-17 20:22:51 | Cannot use all four trigger events at once |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-06-17 23:03:26 | Re: Named transaction |
| Previous Message | Greg Stark | 2009-06-17 22:32:40 | Re: Determining client_encoding from client locale |