Re: Bug with foreign keys and importing from a pg_dump file?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: mdavis(at)sevainc(dot)com
Cc: Philip Warner <pjw(at)rhyme(dot)com(dot)au>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Bug with foreign keys and importing from a pg_dump file?
Date: 2001-01-27 07:09:21
Message-ID: 20851.980579361@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Michael Davis <mdavis(at)sevainc(dot)com> writes:
> Is there a bug with importing from a pg_dump file and foreign keys? If I
> create two tables where one table has a foreign key relationship to the
> other and look at the system tables everything looks great. If I then
> pg_dump, dropdb, createdb, and import the dump file, then the system tables
> are reporting the foreign key differently.

It looks like pg_dump neglects to emit a "FROM pktable" clause in its
CREATE CONSTRAINT TRIGGER commands, and so the tgconstrrelid field of
pg_trigger is not restored. This is a bug I think, although the side
effects appear to be minor...

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message doj 2001-01-27 14:02:05 memory leak in date_part() function in v7.1beta3 ?
Previous Message Bruce Momjian 2001-01-27 04:29:09 Re: Re: Postgres int rounding