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
> 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.
In response to
pgsql-hackers by date
|Next:||From: Andreas Pflug||Date: 2003-09-29 09:14:02|
|Subject: Re: pg_get_ruledef and extra line breaks|
|Previous:||From: Peter Eisentraut||Date: 2003-09-29 08:07:57|
|Subject: Re: pg_dump no longer honors --no-reconnect|
pgsql-general by date
|Next:||From: Bjørn T Johansen||Date: 2003-09-29 09:11:55|
|Subject: Time problem again?|
|Previous:||From: Gezeala 'Eyah' Bacuo II||Date: 2003-09-29 07:47:05|
|Subject: numeric rounding|