Re: Truncate Triggers

Поиск
Список
Период
Сортировка
От Decibel!
Тема Re: Truncate Triggers
Дата
Msg-id 20080131071214.GF1212@decibel.org
обсуждение исходный текст
Ответ на Re: Truncate Triggers  (Alvaro Herrera <alvherre@commandprompt.com>)
Ответы Re: Truncate Triggers  (Simon Riggs <simon@2ndquadrant.com>)
Re: Truncate Triggers  (Gregory Stark <stark@enterprisedb.com>)
Список 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@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable
Следующее
От: Decibel!
Дата:
Сообщение: Re: [PATCHES] Better default_statistics_target