pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bob Smith <bsmith@h-e.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: Referential constraints in version 8
Date: Fri, 15 Apr 2005 09:38:19 -0400
Message-ID: <2590.1113572299@sss.pgh.pa.us> (raw)
In-Reply-To: <db0520ee559ed61f9457ba56c3453a68@h-e.com>
References: <db0520ee559ed61f9457ba56c3453a68@h-e.com>

Bob Smith <bsmith@h-e.com> writes:
> 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?

Yeah, you should --- if it shows as a trigger then the system hasn't
fully grokked it.  The contrib/adddepend script may help you.

			regards, tom lane



view thread (3+ messages)

Message-ID: <2590.1113572299@sss.pgh.pa.us>
Permalink:  ../2590.1113572299@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/2590.1113572299@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, bsmith@h-e.com
  Subject: Re: Referential constraints in version 8
  In-Reply-To: <2590.1113572299@sss.pgh.pa.us>
  References: <db0520ee559ed61f9457ba56c3453a68@h-e.com> <2590.1113572299@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox