From: Ron Mayer <rm_pg@cheapcomplexdevices.com>
To: Gregory Stark <stark@enterprisedb.com>
Cc: Joshua D. Drake <jd@commandprompt.com>
Cc: pgsql-hackers@postgresql.org, "Decibel!" <decibel@decibel.org>
Cc: Josh Berkus <josh@agliodbs.com>
Subject: Re: Overhauling GUCS
Date: Tue, 10 Jun 2008 11:39:08 -0700
Message-ID: <484ECA4C.20004@cheapcomplexdevices.com> (raw)
In-Reply-To: <87hcc3le52.fsf@oxford.xeocode.com>
References: <48409D1E.3070208@agliodbs.com>
<29525.1212613052@sss.pgh.pa.us>
<200806061435.01196.peter_e@gmx.net>
<200806061624.29105.xzilla@users.sourceforge.net>
<8358.1212797962@sss.pgh.pa.us>
<1212800891.14299.35.camel@jd-laptop>
<87hcc3le52.fsf@oxford.xeocode.com>
Gregory Stark wrote:
> "Joshua D. Drake" <jd@commandprompt.com> writes:
>> ...default_statistics_target?"..."Uhh 10."
>
> Ah, but we only ever hear about the cases where it's wrong of course. In other
> words even if we raised it to some optimal value we would still have precisely
> the same experience of seeing only posts on list about it being insufficient.
Yet if it was raised above the optimal, wouldn't you expect to hear cases
where it was too high?
It seems a slow painful way of finding a good setting might be to
keep increasing it until we had cases where the lists start telling
people they need to lower the parameter?
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: rm_pg@cheapcomplexdevices.com, stark@enterprisedb.com, jd@commandprompt.com, decibel@decibel.org, josh@agliodbs.com
Subject: Re: Overhauling GUCS
In-Reply-To: <484ECA4C.20004@cheapcomplexdevices.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox