Skip site navigation (1) Skip section navigation (2)

Re: Truncate Triggers

From: Decibel! <decibel(at)decibel(dot)org>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Truncate Triggers
Date: 2008-01-31 07:12:15
Message-ID: 20080131071214.GF1212@decibel.org (view raw or flat)
Thread:
Lists: pgsql-hackers
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.
-- 
Decibel!, aka Jim C. Nasby, Database Architect  decibel(at)decibel(dot)org 
Give your computer some brain candy! www.distributed.net Team #1828

In response to

Responses

pgsql-hackers by date

Next:From: Decibel!Date: 2008-01-31 07:28:24
Subject: Re: [PATCHES] Better default_statistics_target
Previous:From: Tom LaneDate: 2008-01-31 05:45:40
Subject: Re: Oops - BF:Mastodon just died

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group