On Sat, Sep 6, 2008 at 2:29 AM, Euler Taveira de Oliveira <euler@timbira.com> wrote:
Martin Pihlak escreveu:
> I suspected that, but somehow managed to overlook it :( I guess it was > too tempting to use it. I'll start looking for alternatives. >
If you can't afford a 500 msec pgstat time, then you need to make it tunable.
Additional parameter in config file. Not good.
Another ideas are (i) turn on/off pgstat per table or database and (ii) make the pgstat time tunable per table or database. You can use the reloptions column to store these info. These workarounds are much simpler than that you proposed and they're almost for free.
Does not seem simple to me. Why would dba's want extra management work. We want all the stats to be there as we don't know when we need to look at it.
