| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Triggers on system tables |
| Date: | 2004-02-12 03:30:31 |
| Message-ID: | 26309.1076556631@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
It might be feasible to allow AFTER triggers on system tables, since
those don't actually fire until end of statement, at which point things
are hopefully consistent again. I don't even want to think about
allowing BEFORE triggers.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gavin Sherry | 2004-02-12 03:45:25 | Re: Triggers on system tables |
| Previous Message | Tom Lane | 2004-02-12 03:12:15 | Re: 7.4 - FK constraint performance |