On Thu, 2008-01-31 at 01:12 -0600, Decibel! wrote: > On Mon, Jan 28, 2008 at 09:09:13PM -0300, Alvaro Herrera wrote: > > 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? > > CLUSTER isn't DDL. Most forms of ALTER TABLE are. And CREATE blah, etc. > > My point is that people have been asking for triggers that fire when > specific commands are executed for a long time; it would be > short-sighted to come up with a solution that only works for TRUNCATE if > we could instead come up with a more generic solution that works for a > broader class of (or perhaps all) commands.
Seems a fair comment. What set of commands would you want to fire triggers for, and why? -- Simon Riggs 2ndQuadrant http://www.2ndQuadrant.com ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org
