From: | Jan Wieck <janwieck(at)yahoo(dot)com> |
---|---|
To: | Hans-Juergen Schoenig <hs(at)cybertec(dot)at> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Triggers and System Tables |
Date: | 2002-04-16 15:59:30 |
Message-ID: | 200204161559.g3GFxUB11548@saturn.janwieck.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hans-Juergen Schoenig wrote:
> I have a brief question concerning triggers and system tables:
> Why is it not allowed to trigger a system table? I guess it could be
> useful from time to time.
Because system tables are often modified by direct heap
access, rather than regular query plans handled through the
executor. The direct heap access doesn't invoke the triggers.
Even if we get this problem "fixed" (I don't really consider
it broken), what if you setup a ON UPDATE OR DELETE trigger
for pg_proc, that is broken? You cannot remove or fix it any
more, so your pg_proc system catalog is frozen, forever,
irreversable, infinitely! That's bad!
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
From | Date | Subject | |
---|---|---|---|
Next Message | Lincoln Yeoh | 2002-04-16 16:05:41 | Re: Large table update/vacuum PLEASE HELP! |
Previous Message | Michael Klatt | 2002-04-16 15:57:33 | Re: Perplexing Query Performance |