| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | edoardo(dot)innocenti(at)savinodelbene(dot)com |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: TopMemoryContext - Configuration Mistake? |
| Date: | 2010-08-17 13:44:57 |
| Message-ID: | 9280.1282052697@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Edoardo Innocenti <edoardo(dot)innocenti(at)savinodelbene(dot)com> writes:
> Query Plan:<br>
> "HashAggregate (cost=4910.06..4910.19 rows=1 width=659)"
Hm ... the planner seems to think that this is a small query that isn't
going to take long, which is a bit at odds with the fact that you're
running out of memory. I suspect that these rowcount estimates are
far too low, which would suggest that you need to make sure your
ANALYZE statistics are up-to-date, and perhaps raise the statistics
targets. Try to get the plan's estimated rowcounts to approximate
reality.
BTW, you might want to think about turning off your mail program's
HTML option. What other people are seeing looks like this:
http://archives.postgresql.org/pgsql-admin/2010-08/msg00126.php
and it's not pretty.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gnanakumar | 2010-08-17 14:07:49 | Re: SQL statements not printed in pgpool log |
| Previous Message | Edoardo Innocenti | 2010-08-17 06:58:00 | Re: TopMemoryContext - Configuration Mistake? |