X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id EC8855281E for ; Wed, 15 Jun 2005 14:33:29 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 56505-03 for ; Wed, 15 Jun 2005 17:33:23 +0000 (GMT) Received: from srv1.alteeve.com (unknown [209.167.86.38]) by svr1.postgresql.org (Postfix) with ESMTP id B026F5280C for ; Wed, 15 Jun 2005 14:33:21 -0300 (ADT) Received: from [192.168.1.99] (nabiki.thelinuxexperience.com [209.167.86.34]) by srv1.alteeve.com (8.12.10/8.12.10) with ESMTP id j5FI2Ipe025858; Wed, 15 Jun 2005 14:02:19 -0400 Message-ID: <42B06660.1060504@alteeve.com> Date: Wed, 15 Jun 2005 13:33:20 -0400 From: Madison Kelly User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Debian/1.7.8-1 X-Accept-Language: en-us, en, ja MIME-Version: 1.0 To: karim.nassar@acm.org Cc: pgsql-performance@postgresql.org Subject: Re: Index ot being used References: <1825.216.209.137.1.1118419819.squirrel@mail.alteeve.com> <20050610155535.GO8451@tobias.nordicbet.com> <42AC42CB.8050703@alteeve.com> <24636.1118591783@sss.pgh.pa.us> <42ACBC95.9020404@alteeve.com> <20050613030001.GB17491@wolff.to> <20050613031317.GA18988@wolff.to> <42AD008D.4080600@alteeve.com> <20050613035346.GA20703@wolff.to> <42AD0B94.9090508@alteeve.com> <20050613132852.GA31142@wolff.to> <42ADC77B.7000007@alteeve.com> <22127.1118686403@sss.pgh.pa.us> <42ADD8DC.1000001@alteeve.com> <3643.1118696404@sss.pgh.pa.us> <42ADFAF8.7080107@alteeve.com> <1118854322.7135.133.camel@localhost.localdomain> In-Reply-To: <1118854322.7135.133.camel@localhost.localdomain> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200506/333 X-Sequence-Number: 12970 Karim Nassar wrote: > Your goal is admirable. However, many people tweak their postgresql.conf > files, and your program can't know whether or not this has happened. It > might be a good idea to have a var $do_db_optimization, which defaults > to on. Then, if your users have trouble or are advanced admins they can > turn it off. My personal opinion is that there are too many > architectures and configurations for you to accurately optimize inside > your program, and this gives you and your users an easy out. > > if ($do_db_optimization == 1) { > $DB->do("SET ENABLE_SEQSCAN TO OFF") || die... > } else { > # do nothing -- postgresql will figure it out > } That is a wonderful idea and I already have the foundation in place to easily implement this. Thanks!! Madison -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Madison Kelly (Digimer) TLE-BU, The Linux Experience; Back Up http://tle-bu.thelinuxexperience.com -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-