| From: | Ang Chin Han <angch(at)bytecraft(dot)com(dot)my> |
|---|---|
| To: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
| Cc: | Rhaoni Chiu Pereira <rhaoni(at)sistemica(dot)info>, PostgreSQL Performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Query too slow |
| Date: | 2003-08-26 06:49:17 |
| Message-ID: | 3F4B02ED.4080704@bytecraft.com.my |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Stephan Szabo wrote:
> Looking at the explain:
Veering aside a bit, since we usually pinpoint performance problems by
looking at EXPLAIN ANALYZE's differences between the planner's
estimation and actual execution's stats, what's involved in parsing the
EXPLAIN ANALYZE results, and highlighting the places where they are way
different? Bold, underline, or put some asterisks in front of those steps.
Makes looking at big EXPLAIN ANALYZE trees much easier.
--
Linux homer 2.4.18-14 #1 Wed Sep 4 13:35:50 EDT 2002 i686 i686 i386
GNU/Linux
2:30pm up 243 days, 5:48, 8 users, load average: 5.52, 5.29, 5.10
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bupp Phillips | 2003-08-26 09:18:23 | Re: What is the fastest way to get a resultset |
| Previous Message | Marc G. Fournier | 2003-08-26 06:01:26 | Re: Replication Ideas |