| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "George Woodring" <george(dot)woodring(at)iglass(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Foreign Key written as a trigger |
| Date: | 2005-07-11 14:17:18 |
| Message-ID: | 8197.1121091438@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"George Woodring" <george(dot)woodring(at)iglass(dot)net> writes:
> I have a database that has been upgrade numerous times (Started about
> 7.1 and is not 7.4.8). The table has 2 foreign keys on it, but when I
> look at the table I see that the FK applied before 7.4.X is written as a
> trigger. Everything seems to work, I was just wondering if there are
> any performance reasons to change the trigger to a FK.
I don't think it would have any performance impact, but it'd definitely
be more future-proof to hide the triggers. See contrib/adddepend for
a possibly helpful tool.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2005-07-11 14:22:38 | Re: Transaction isolation levels |
| Previous Message | George Woodring | 2005-07-11 13:58:11 | Foreign Key written as a trigger |