| From: | Bob Smith <bsmith(at)h-e(dot)com> | 
|---|---|
| To: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> | 
| Subject: | Referential constraints in version 8 | 
| Date: | 2005-04-15 07:31:28 | 
| Message-ID: | db0520ee559ed61f9457ba56c3453a68@h-e.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-admin | 
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(at)h-e(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc Cousin | 2005-04-15 10:04:57 | Online backups and WAL | 
| Previous Message | Theo Galanakis | 2005-04-15 02:14:20 | Latest pg_autovacuum script |