From: Stephan Szabo <sszabo@megazone.bigpanda.com>
To: BenLaKnet <benlaknet@icqmail.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: [pg-sql] - Problem with duplicate table (PostgreSQL 7.2.3
Date: Mon, 11 Aug 2003 06:48:31 -0700 (PDT)
Message-ID: <20030811064449.D72304-100000@megazone.bigpanda.com> (raw)
In-Reply-To: <3F379DA8.7040501@icqmail.com>
On Mon, 11 Aug 2003, BenLaKnet wrote:
> we make a dump before ... and with a product pgmanager (ems tech) we do
> not show any foreign keys.
That's possible, I'd have guessed that it should be dumping the triggers
as CREATE CONSTRAINT TRIGGER commands in the dump.
> But I think all of triggers of referenced table are not deleted.
If you can make a repeatable test case (a simpler one than your full data
set) that'd be helpful to look at. One possibility is that older versions
(7.1 and earlier) had a bug that would cause the constraint triggers to be
reloaded without the information of which table it was associated with,
but I don't see how that'd apply here.
> We recreate the schemas ... and now it's running.
>
> How is it possible to identify Triggers with no referenced tables ?
Generally you'd need to look through pg_trigger manually looking for
something that doesn't match up correctly against the constraints you
expect to have.
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 using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: sszabo@megazone.bigpanda.com, benlaknet@icqmail.com
Subject: Re: [pg-sql] - Problem with duplicate table (PostgreSQL 7.2.3
In-Reply-To: <20030811064449.D72304-100000@megazone.bigpanda.com>
* 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