| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Mark Lewis <mark(dot)lewis(at)mir3(dot)com> |
| Cc: | Arnaud Lesauvage <thewild(at)freesurf(dot)fr>, Ragnar <gnari(at)hive(dot)is>, Jens Schipkowski <jens(dot)schipkowski(at)apus(dot)co(dot)at>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Slow update with simple query |
| Date: | 2006-12-14 16:50:26 |
| Message-ID: | 21627.1166115026@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Mark Lewis <mark(dot)lewis(at)mir3(dot)com> writes:
> Out of curiosity, how hard would it be to modify the output of EXPLAIN
> ANALYZE when doing an insert/update to include the index update times
> and/or non-FK constraint checking times and/or the table row update
> times?
I don't think it'd help much --- in an example like this, other tools
like vmstat would be more likely to be useful in investigating the
problem. There's also the problem that EXPLAIN ANALYZE overhead is
already too high --- another dozen gettimeofday() calls per row
processed doesn't sound appetizing.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rohit Prakash Khare | 2006-12-14 17:13:45 | unsubscribe |
| Previous Message | Tom Lane | 2006-12-14 16:41:15 | Re: EXPLAIN ANALYZE on 8.2 |