| From: | Rod Taylor <pg(at)rbt(dot)ca> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Triggers on system tables |
| Date: | 2004-02-12 03:51:15 |
| Message-ID: | 1076557874.761.212.camel@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2004-02-11 at 22:30, Tom Lane wrote:
> Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> writes:
> > There have been a few discussions about triggers on system tables in
> > the past and the problems with such triggers seem to be:
>
> I think the killer problem is that we couldn't allow triggers on system
> tables to do very much. By definition, the database is in an inconsistent
> state if we are in the middle of updating system tables. We can't allow
> arbitrary bits of SQL to run then.
Yes, the internal calls from one command to another make this tricky --
but the return Tag is set very early for the statement. Could the Before
trigger for system commands (CREATE, ALTER, etc.) not be kicked of in
the same area as the tag is set?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-02-12 04:11:27 | Re: Triggers on system tables |
| Previous Message | Gavin Sherry | 2004-02-12 03:45:25 | Re: Triggers on system tables |