Re: raising the default default_statistics_target

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: josh(at)agliodbs(dot)com, pgsql-hackers(at)postgresql(dot)org, Neil Conway <neilc(at)samurai(dot)com>
Subject: Re: raising the default default_statistics_target
Date: 2004-03-08 18:28:46
Message-ID: 200403081828.i28ISkb01400@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Josh Berkus <josh(at)agliodbs(dot)com> writes:
> > It is. I've found that "problem" queries, especially those caused by real,
> > uneven distribution of data, require raising statistics to 150-400 in order
> > to fix. This is much to high a level to assign as a default.
>
> That's basically what's bothering me about the suggestion to increase to
> 25 --- I'm dubious that it will do any good.
>
> > Further, in 7.5 we'll be introducing correlated stats for multi-column indexes
> > (unless something's gone off with that?)
>
> News to me. It's certainly not there now.
>
> > This will then give indexed columns "automatically" a somewhat higher
> > level of stats analysis than other columns.
>
> That is potentially a good idea. There's still the question of what is
> a reasonable default, though.

Do all the columns have to have the same number of statistics buckets?
Could that stats collector adjust the number of buckets based on the
data somehow?

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-03-08 18:37:53 Re: raising the default default_statistics_target
Previous Message Kurt Roeckx 2004-03-08 18:12:00 Re: socket calls in signal handler (WAS: APC + socket restrictions un der Win32?)