From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
Cc: | "PostgreSQL Hackers Mailing List" <pgsql-hackers(at)postgresql(dot)org>, "Didier Moens" <moensd(at)xs4all(dot)be> |
Subject: | Re: Foreign key wierdness |
Date: | 2003-01-20 16:07:44 |
Message-ID: | 3487.1043078864@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> writes:
> Thing is Tom, this issue can be reproduced *every* time, without fail.
And have you vacuumed or analyzed yet? Or possibly you are short an
index or two (you really need indexes on both the referencing and
referenced columns).
> I've been looking at his for some time now (couple of weeks or more),
> and the only thing I can find is the SELECT ... FOR UPDATE in the
> PostgreSQL logs that I quoted. These exactly follow *every* fkey
> creation, and are definately not issued by pgAdmin.
No, I told you: those are the internal verification query (it comes from
RI_FKey_check_ins(), if you want to look).
If you really think the schema qualification has something to do with
it, try issuing the ADD FOREIGN KEY command manually in psql, with and
without schema name.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2003-01-20 17:01:46 | Re: Foreign key wierdness |
Previous Message | Dave Page | 2003-01-20 15:47:51 | Re: Foreign key wierdness |