Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 635C92E0032 for ; Tue, 10 Jun 2008 15:39:22 -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 67479-02 for ; Tue, 10 Jun 2008 15:39:17 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from smtp106.biz.mail.mud.yahoo.com (smtp106.biz.mail.mud.yahoo.com [68.142.200.254]) by developer.postgresql.org (Postfix) with SMTP id 798C52E002C for ; Tue, 10 Jun 2008 15:39:18 -0300 (ADT) Received: (qmail 36903 invoked from network); 10 Jun 2008 18:39:16 -0000 Received: from unknown (HELO ?192.168.5.105?) (ramayer@forensiclogic.com@76.202.61.167 with plain) by smtp106.biz.mail.mud.yahoo.com with SMTP; 10 Jun 2008 18:39:16 -0000 X-YMail-OSG: V_SlUjIVM1kQDiAa4BU.zCuYoSFYL6oWA.8LcP563IL4fjijEiwZf8CtPCr.ofx7o7ze3uBBhHPSqK_lD7pCGQlrsHXnmt67bHVIaZ9mPs4K6TxZEfrewFVPHFtVbdjVr3A- X-Yahoo-Newman-Property: ymail-3 Message-ID: <484ECA4C.20004@cheapcomplexdevices.com> Date: Tue, 10 Jun 2008 11:39:08 -0700 From: Ron Mayer User-Agent: Mozilla-Thunderbird 2.0.0.14 (X11/20080509) MIME-Version: 1.0 To: Gregory Stark CC: "Joshua D. Drake" , pgsql-hackers@postgresql.org, "Decibel!" , Josh Berkus Subject: Re: Overhauling GUCS 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> In-Reply-To: <87hcc3le52.fsf@oxford.xeocode.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/475 X-Sequence-Number: 119588 Gregory Stark wrote: > "Joshua D. Drake" 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?