From: | "Warren Little" <warren(dot)little(at)reardeninc(dot)com> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | BUG #1930: Cannot create foreign key constraint |
Date: | 2005-10-01 15:32:21 |
Message-ID: | 20051001153221.490C0F0D5F@svr2.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged online:
Bug reference: 1930
Logged by: Warren Little
Email address: warren(dot)little(at)reardeninc(dot)com
PostgreSQL version: 8.0.3
Operating system: 2.6.10-1.770_FC3smp #1 SMP Thu Feb 24 18:36:43 EST 2005
x86_64 x86_64 x86_64 GNU/Linux
Description: Cannot create foreign key constraint
Details:
pg_restore generates the following error:
pg_restore: [archiver (db)] Error from TOC entry 2950; 16386 17827531 FK
CONSTRA INT asientry_r0 tigris
pg_restore: [archiver (db)] could not execute query: ERROR: insert or
update on table "asientry" violates foreign key constraint "asientry_r0"
DETAIL: Key (pid)=(AA0003403544) is not present in table "pobject".
Command was: ALTER TABLE ONLY asientry
ADD CONSTRAINT asientry_r0 FOREIGN KEY (pid) REFERENCES pobject(pid);
Also running the alter table after restore generates same constraint
violation error.
The following query returns one row:
select * from asientry, pobject
where pobject.pid = 'AA0003403544'
and pobject.pid = asientry.pid;
Any ideas
From | Date | Subject | |
---|---|---|---|
Next Message | Devrim GUNDUZ | 2005-10-01 15:35:36 | BUG #1931: ILIKE and LIKE fails on Turkish locale |
Previous Message | Gaetano Mendola | 2005-10-01 11:48:38 | Re: BUG #1927: incorrect timestamp returned |