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

Re: Truncate Triggers

From: Decibel! <decibel(at)decibel(dot)org>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Truncate Triggers
Date: 2008-01-25 17:49:34
Message-ID: 20080125174934.GI37748@decibel.org (view raw or flat)
Thread:
Lists: pgsql-hackers
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).

The reason I put triggers in quotes is because I'm not suggesting that
we actually put triggers on the catalog tables, since we all know that's
hard/impossible. Instead this would have to tie into command processing,
similar to what you're proposing for truncate.
-- 
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: Zdenek KotalaDate: 2008-01-25 18:03:10
Subject: Re: Proposal: Integrity check
Previous:From: Tom LaneDate: 2008-01-25 17:27:22
Subject: Re: Proposal: Integrity check

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