| From: | "Peter Koczan" <pjkoczan(at)gmail(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Alvaro Herrera" <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Legacy foreign keys |
| Date: | 2008-02-02 19:43:15 |
| Message-ID: | 4544e0330802021143n2d38dce8k4ff9ab271aa35c2a@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> Yeah, it's expecting to see a set of three related triggers. For
> instance, if I do this in a 7.0 database:
> ...
> If your original database doesn't have all three triggers, then you had
> a problem already --- the FK constraint wasn't being enforced properly.
Ah, these were from before I became the main database admin. It was
probably some previous admin or programmer who thought he could be
clever and drop the other FK-related triggers.
> In 8.3, you could look for the pg_trigger entries with zero tgconstraint
> values. However, prior versions don't have that column; you'd have to
> look instead for entries that aren't linked to a pg_constraint entry
> by a pg_depend entry.
Thanks again, I should have enough info to fix this now.
Peter
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-02-02 20:36:15 | Re: Legacy foreign keys |
| Previous Message | Tom Lane | 2008-02-01 23:53:00 | Re: Legacy foreign keys |