| From: | Greg Smith <greg(at)2ndquadrant(dot)com> |
|---|---|
| To: | felix <crucialfelix(at)gmail(dot)com> |
| Cc: | sthomas(at)peak6(dot)com, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Really really slow select count(*) |
| Date: | 2011-02-04 18:38:05 |
| Message-ID: | 4D4C478D.9070909@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
felix wrote:
> and do you agree that I should turn CLUSTER ON ?
> I have no problem to stop all tasks to this table at night and just
> reload it
You don't turn it on; it's a one time operation that does a cleanup. It
is by far the easiest way to clean up the mess you have right now.
Moving forward, if you have max_fsm_pages set to an appropriate number,
you shouldn't end up back in this position again. But VACUUM along
won't get you out of there, and VACUUM FULL is always a worse way to
clean this up than CLUSTER.
--
Greg Smith 2ndQuadrant US greg(at)2ndQuadrant(dot)com Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us
"PostgreSQL 9.0 High Performance": http://www.2ndQuadrant.com/books
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-02-04 18:48:32 | Re: [HACKERS] Slow count(*) again... |
| Previous Message | Shaun Thomas | 2011-02-04 18:34:42 | Re: Really really slow select count(*) |