Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 32A712E0046 for ; Fri, 6 Jun 2008 22:08:19 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 51039-01 for ; Fri, 6 Jun 2008 22:08:11 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by developer.postgresql.org (Postfix) with ESMTP id 208FB2E0049 for ; Fri, 6 Jun 2008 22:08:15 -0300 (ADT) Received: from [192.168.1.5] (or-69-34-217-90.sta.embarqhsd.net [69.34.217.90]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m5719QmT024981 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 6 Jun 2008 18:09:27 -0700 Subject: Re: Overhauling GUCS From: "Joshua D. Drake" To: Tom Lane Cc: Robert Treat , pgsql-hackers@postgresql.org, Peter Eisentraut , Greg Smith , Andreas Pflug , Decibel! , Josh Berkus In-Reply-To: <8358.1212797962@sss.pgh.pa.us> 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> Content-Type: text/plain Organization: Command Prompt, Inc. Date: Fri, 06 Jun 2008 18:08:11 -0700 Message-Id: <1212800891.14299.35.camel@jd-laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.22.1.1 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Fri, 06 Jun 2008 18:09:36 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/337 X-Sequence-Number: 119450 On Fri, 2008-06-06 at 20:19 -0400, Tom Lane wrote: > Robert Treat writes: > Actually, the reason it's still 10 is that the effort expended to get it > changed has been *ZERO*. I keep asking for someone to make some > measurements, do some benchmarking, anything to make a plausible case > for a specific higher value as being a reasonable place to set it. > The silence has been deafening. Not surprising really. It is a simple adjustment to make and it also is easy to spot when its a problem. However it is not trivial to test for (in terms of time and effort). I know 10 is wrong and so do you. If you don't I am curious why I see so many posts from you saying, "Your estimates are off, what is your default_statistics_target?" with yet even more responses saying, "Uhh 10." Sincerely, Joshua D. Drake