From: | Richard Huxton <dev(at)archonet(dot)com> |
---|---|
To: | Andrew Nesheret <andrew(at)infinet(dot)ru> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: foreign key constraint, planner ignore index. |
Date: | 2007-12-20 13:42:08 |
Message-ID: | 476A7130.5070306@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Andrew Nesheret wrote:
> Richard Huxton wrote:
>> Richard Huxton wrote:
>>>
>>> I'm putting together a small test case to see if I can reproduce your
>>> behaviour here.
>>
>> Does the attached small script misbehave in the same way as your real
>> data? From here it works fine when the fkey is ON ... RESTRICT.
>>
>> I'm right in thinking that your "nodes" fkey is RESTRICT on update and
>> delete?
>>
> You script is worked fine on same database, where is difference?
Good question. There *must* be a difference. Why can't either of us see it?
1. Try adding another 5 million rows to the test "traffic" table and see
if that makes any difference. It shouldn't.
2. Run a "vacuum verbose sf_ipv4traffic" and see if there's a lot of
dead rows. I shouldn't have thought there are.
We might want to move this to the performance mailing-list, and see if
anyone has an idea over there.
--
Richard Huxton
Archonet Ltd
From | Date | Subject | |
---|---|---|---|
Next Message | Glyn Astill | 2007-12-20 13:49:19 | Slony I - removing a replication set |
Previous Message | Alvaro Herrera | 2007-12-20 13:27:05 | Re: Quick Regex Question |