Re: Revisiting default_statistics_target

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, Mark Wong <markwkm(at)gmail(dot)com>, Greg Smith <gsmith(at)gregsmith(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Revisiting default_statistics_target
Date: 2009-06-07 16:53:55
Message-ID: 1244393635.15799.49.camel@ebony.2ndQuadrant
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On Sun, 2009-06-07 at 12:13 -0400, Tom Lane wrote:

> In any case, what we seem to have here is evidence that there are some
> cases where the new default value of default_statistics_target is too
> high and you can get a benefit by lowering it. I'm not sure we should
> panic about that. Default values ought to be compromises. If people
> only ever change the default in one direction then it's probably not a
> very good compromise. We know that there are applications for which
> 100 is still too low, so maybe now we have got the pain spread out
> roughly evenly...

I'm certainly happy with 100 as the default.

--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2009-06-07 17:03:09 Re: Partial vacuum versus pg_class.reltuples
Previous Message Tom Lane 2009-06-07 16:36:03 Re: pg_migrator issue with contrib