Re: ADD FOREIGN KEY (was Re: [GENERAL] 7.4Beta)
От | Hannu Krosing |
---|---|
Тема | Re: ADD FOREIGN KEY (was Re: [GENERAL] 7.4Beta) |
Дата | |
Msg-id | 1064829433.2645.2.camel@fuji.krosing.net обсуждение исходный текст |
Ответ на | Re: ADD FOREIGN KEY (was Re: [GENERAL] 7.4Beta) (Andreas Pflug <pgadmin@pse-consulting.de>) |
Ответы |
Re: ADD FOREIGN KEY (was Re: [GENERAL] 7.4Beta)
|
Список | 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
В списке pgsql-hackers по дате отправления: