Re: BUG #1930: Cannot create foreign key constraint

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: BUG #1930: Cannot create foreign key constraint
Дата
Msg-id 3409.1128266336@sss.pgh.pa.us
обсуждение исходный текст
Ответ на BUG #1930: Cannot create foreign key constraint  ("Warren Little" <warren.little@reardeninc.com>)
Список pgsql-bugs
"Warren Little" <warren.little@reardeninc.com> writes:
> 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;

That seems a bit odd.  Are the two pid columns exactly the same datatype
(and what is it anyway)?  What plan does EXPLAIN show for that SELECT,
and what plan do you see for

SELECT fk.pid FROM ONLY asientry fk
  LEFT OUTER JOIN ONLY pobject pk
  ON pk.pid=fk.pid
  WHERE pk.pid IS NULL AND fk.pid IS NOT NULL;

(which is what is probably being used to test foreign key validity)?

            regards, tom lane

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: BUG #1932: initdb.log
Следующее
От: "Duncan Crombie"
Дата:
Сообщение: BUG #1933: ADD COLUMN with DEFAULT resets table oids