| From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
|---|---|
| To: | vjoshi(at)zetainteractive(dot)com, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, Varadharajan Mukundan <srinathsmn(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Performance issues |
| Date: | 2015-03-17 11:45:17 |
| Message-ID: | 550813CD.7040605@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 17.3.2015 12:07, Vivekanand Joshi wrote:
> EXPLAIN ANALYZE didn't give result even after three hours.
In that case the only thing you can do is 'slice' the query into smaller
parts (representing subtrees of the plan), and analyze those first. Look
for misestimates (significant differences between estimated and actual
row counts, and very expensive parts).
We can't do that, because we don't have your data or queries, and
without the explain analyze it's difficult to give advices.
--
Tomas Vondra http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vivekanand Joshi | 2015-03-17 12:05:46 | Re: Performance issues |
| Previous Message | Tomas Vondra | 2015-03-17 11:42:06 | Re: Performance issues |