| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Decibel! <decibel(at)decibel(dot)org> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Truncate Triggers |
| Date: | 2008-01-29 00:09:13 |
| Message-ID: | 20080129000913.GG1817@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Decibel! wrote:
> On Fri, Jan 25, 2008 at 11:40:19AM +0000, Simon Riggs wrote:
> > (for 8.4 ...)
> > I'd like to introduce triggers that fire when we issue a truncate:
>
> Rather than focusing exclusively on TRUNCATE, how about "triggers" that
> fire whenever any kind of DDL operation is performed? (Ok, truncate is
> more DML than DDL, but still).
I don't think it makes sense in general. For example, would we fire
triggers on CLUSTER? Or on ALTER TABLE / SET STATISTICS?
TRUNCATE seems a special case that needs it.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Mayer | 2008-01-29 00:13:09 | Re: [PATCHES] Proposed patch: synchronized_scanning GUCvariable |
| Previous Message | Alvaro Herrera | 2008-01-28 23:59:09 | Re: Strange locking choices in pg_shdepend.c |