From: | Hannu Krosing <hannu(at)tm(dot)ee> |
---|---|
To: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ADD FOREIGN KEY (was Re: [GENERAL] 7.4Beta) |
Date: | 2003-09-29 09:57:13 |
Message-ID: | 1064829433.2645.2.camel@fuji.krosing.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Andreas Pflug kirjutas E, 29.09.2003 kell 12:04:
> Christopher Kings-Lynne wrote:
>
> > You could just as easily argue that the lack of integrity testing at
> > data load time was equally a bug.
> >
> > I think we need someway of telling postgres to suppress a foreign key
> > check.
> >
> > The main problem is that the foreign key column is often not indexed.
>
> So a db designer made a bloody mistake.
> The problem is there's no easy way to find out what's missing.
> I'd really like EXPLAIN to display all subsequent triggered queries
> also, to see the full scans caused by missing indexes.
It could probably be doable for EXPLAIN ANALYZE (by actually tracing
execution), but then you will see really _all_ queries, i.e. for a 1000
row update you would see 1 UPDATE query and 1000 fk checks ...
OTOH, you probably can get that already from logs with right logging
parameters.
-------------
Hannu
From | Date | Subject | |
---|---|---|---|
Next Message | strk | 2003-09-29 10:05:10 | finding memory leaks in extensions |
Previous Message | Kris Jurka | 2003-09-29 09:52:51 | Re: PostgreSQL SSL communication with SecureTcpClient (Ssl |
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2003-09-29 10:28:44 | Re: ADD FOREIGN KEY (was Re: [GENERAL] 7.4Beta) |
Previous Message | Christopher Kings-Lynne | 2003-09-29 09:44:35 | pg_dump permissions problem |