X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 75FA053F7C for ; Fri, 15 Apr 2005 04:31:35 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 99436-03 for ; Fri, 15 Apr 2005 07:31:29 +0000 (GMT) Received: from h-e.com (h-68-166-219-83.snvacaid.covad.net [68.166.219.83]) by svr1.postgresql.org (Postfix) with ESMTP id 6603153FC7 for ; Fri, 15 Apr 2005 04:31:28 -0300 (ADT) Received: from [192.168.42.42] (HELO [192.168.42.42]) by h-e.com (CommuniGate Pro SMTP 4.2.9) with ESMTP id 1148210 for pgsql-admin@postgresql.org; Fri, 15 Apr 2005 00:31:28 -0700 Mime-Version: 1.0 (Apple Message framework v619.2) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; format=flowed To: pgsql-admin From: Bob Smith Subject: Referential constraints in version 8 Date: Fri, 15 Apr 2005 00:31:28 -0700 X-Mailer: Apple Mail (2.619.2) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.05 tagged_above=0 required=5 tests=FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200504/199 X-Sequence-Number: 17212 We have just finished upgrading Postgres from 7.2 to 8, and I must live right or something because there was only one glitch. When the dump from 7.2 was restored into 8, some foreign key references which should have been initially deferred had become non-deferrable. I had to re-define those references by dropping the corresponding triggers and using ALTER TABLE to put them back as foreign key constraints, which seems to have fixed the problem. However, those references which I re-defined now show up explicitly in the table descriptions as foreign key constraints, and the corresponding triggers are not listed. This is great since it makes the table descriptions much more intelligible, but my concern is that all the other references which I didn't re-define still show as triggers and not as foreign key constraints. Is this just a cosmetic issue with psql's table description, or is there actually a functional difference? Should I re-define all the other foreign key constraints to be safe? Thanks! Bob Smith Hammett & Edison, Inc. bsmith@h-e.com