Have you ever done any testing to see if just setting
default_statistics_target to 500 has a negative impact on the system?
On Sep 22, 2006, at 4:48 PM, Cosimo Streppone wrote:
Christian Storm wrote:
At the moment, my rule of thumb is to check out the ANALYZE VERBOSE
messages to see if all
Christian Storm wrote:
At the moment, my rule of thumb is to check out the ANALYZE VERBOSE
messages to see if all table pages are being scanned.
INFO: "mytable": scanned xxx of yyy pages, containing ...
If xxx = yyy, then I keep statistics at the current level.
When xxx is way less than yyy,
Andrew wrote:
On Wed, Sep 20, 2006 at 11:09:23AM +0200, Cosimo Streppone wrote:
I scheduled a cron job every hour or so that runs an analyze on the
4/5 most intensive relations and sleeps 30 seconds between every
analyze.
This suggests to me that your statistics need a lot of updating.
Agre
On Wed, Sep 20, 2006 at 11:09:23AM +0200, Cosimo Streppone wrote:
>
> I scheduled a cron job every hour or so that runs an analyze on the
> 4/5 most intensive relations and sleeps 30 seconds between every
> analyze.
>
> This has optimized db response times when many clients run together.
> I want
Hi all,
I was searching tips to speed up/reduce load on a Pg8 app.
Thank you for all your suggestions on the matter.
Thread is archived here:
http://www.mail-archive.com/pgsql-performance@postgresql.org/msg18342.html
After intensive application profiling and database workload analysis,
I manage
