| From: | Alan McKay <alan(dot)mckay(at)gmail(dot)com> |
|---|---|
| To: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: statement stats extra load? |
| Date: | 2009-09-22 13:19:44 |
| Message-ID: | 844129e80909220619g33e61f54u8eb5dcf51ec74e18@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, Sep 22, 2009 at 2:42 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> That's not true at all.
>
> If you have many relations in your cluster that have at some point been
> touched, the starts collector can create a *significant* load on the I/o
> system. I've come across several cases where the only choice was to disable
> the collector completely, even given all the drawbacks from that.
Thanks Magnus, I thought that other response sounded a bit fanciful :-)
So is there any way to predict the load this will have? Or just try
it and hope for the best? :-)
Right now on our 8.3 system it is off and we'd like to turn it on
--
“Don't eat anything you've ever seen advertised on TV”
- Michael Pollan, author of "In Defense of Food"
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shiva Raman | 2009-09-22 13:54:44 | High CPU load on Postgres Server during Peak times!!!! |
| Previous Message | Aidan Van Dyk | 2009-09-22 13:16:44 | Re: session servers in ram |