| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | erobles <erobles(at)sensacd(dot)com(dot)mx> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: NOTICE: ignoring incomplete trigger group for constraint |
| Date: | 2010-05-21 16:18:59 |
| Message-ID: | 20497.1274458739@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
erobles <erobles(at)sensacd(dot)com(dot)mx> writes:
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
[ Please don't send all-html mail to the lists ]
> I have running postgres 8.3.1 and a dump file from postgers 7.2
> :-P , but when i tried to restore the dump i have the next
> message:
> psql:lostriggers:10: NOTICE: ignoring incomplete trigger group for
> constraint "valida_ent_a_sal" FOREIGN KEY sal_d(tagname_ed) REFERENCES
> ent_a(tagname_ea)
Yeah, this is known to happen in some cases where there was a broken
(incompletely enforced) foreign key constraint in your old database.
The odds are good that what you should do is nothing at all, because
you probably didn't even realize you still had the FK constraint in the
old database: the most common error cases weren't enforced. It's likely
that if you try to add the FK constraint now, you'll find it fails
because the data doesn't even satisfy the constraint. So you could
just leave things alone and the new database will behave approximately
like the old one did. But if you really want to add the FK constraint
back in, ALTER TABLE ADD FOREIGN KEY is the way.
BTW, the known cases for this are follow-on damage from a bug in 7.0
pg_dump. Does the ancestry of this database go back that far?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | erobles | 2010-05-21 17:00:24 | cleaning wal files from postgres |
| Previous Message | Peter Hunsberger | 2010-05-21 16:09:11 | Re: How to lose transaction history (xmin values, WAL, etc.)? |