| From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
|---|---|
| To: | "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ADD FOREIGN KEY (was Re: [GENERAL] 7.4Beta) |
| Date: | 2003-09-29 13:53:13 |
| Message-ID: | 3F783949.9010901@pse-consulting.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Nigel J. Andrews wrote:
>On Mon, 29 Sep 2003, Christopher Kings-Lynne wrote:
>
>
>
>>>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.
>>>
>>>
>>I'd sure second that!
>>
>>
>
>That's only partially determinable though. The trigger code could branch and
>run two different queries depending on the values supplied in the 'input' tuple
>of the trigger.
>
That would be ok; if I got a problem with a certain query, I don't
expect to find problems I might get with other queries. Though this
would be nice, how about a general pg_gimme_all_problems() function :-)
Regards,
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Harald Fuchs | 2003-09-29 14:07:49 | Re: Result set granularity.. |
| Previous Message | ejos | 2003-09-29 13:41:37 | Edward |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc G. Fournier | 2003-09-29 13:56:42 | Re: 2-phase commit |
| Previous Message | Bruce Momjian | 2003-09-29 13:49:58 | Re: pg_dump no longer honors --no-reconnect |