| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: WIP: make EXPLAIN ANALYZE show time spent in triggers |
| Date: | 2005-03-25 07:47:49 |
| Message-ID: | 21221.1111736869@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
>> Right. So what's the point? It seems like the printout would just be
>> useless noise: it'd repeat N times the estimate of the top-level number
>> of output rows.
> Well I guess the point would be to remind people that there are
> (potentially) expensive triggers that will run, so even though the
> analysis presented indicates that the tested query will be fast, it
> might not be...
If we had any way to estimate the costs of the triggers, I'd agree with
listing those numbers --- but the triggers are just black boxes. So I
don't see the point. We might as well just add one line saying
<ding> You've got triggers!
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-03-25 07:48:27 | Re: WIP: make EXPLAIN ANALYZE show time spent in triggers |
| Previous Message | Christopher Kings-Lynne | 2005-03-25 07:44:03 | Re: WIP: make EXPLAIN ANALYZE show time spent in triggers |