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 8E607D1B1BE for ; Fri, 23 Jul 2004 19:01:46 -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 57243-02 for ; Fri, 23 Jul 2004 22:01:42 +0000 (GMT) Received: from mpls-qmqp-01.inet.qwest.net (mpls-qmqp-01.inet.qwest.net [63.231.195.112]) by svr1.postgresql.org (Postfix) with SMTP id ACCC9D1B272 for ; Fri, 23 Jul 2004 19:01:38 -0300 (ADT) Received: (qmail 5277 invoked by uid 0); 23 Jul 2004 22:01:40 -0000 Received: from unknown (63.231.195.13) by mpls-qmqp-01.inet.qwest.net with QMQP; 23 Jul 2004 22:01:40 -0000 Received: from 63-227-127-37.dnvr.qwest.net (HELO ?10.0.0.2?) (63.227.127.37) by mpls-pop-13.inet.qwest.net with SMTP; 23 Jul 2004 22:01:40 -0000 Date: Fri, 23 Jul 2004 16:02:53 -0600 Message-Id: <1090620173.709.66.camel@localhost.localdomain> From: "Scott Marlowe" To: "Jaime Casanova" Cc: pgsql-performance@postgresql.org Subject: Re: [HACKERS] Wrong index choosen? In-Reply-To: <20040723215111.46840.qmail@web50004.mail.yahoo.com> References: <20040723215111.46840.qmail@web50004.mail.yahoo.com> Content-Type: text/plain Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.1 tagged_above=0.0 required=5.0 tests=RCVD_IN_SORBS X-Spam-Level: X-Archive-Number: 200407/159 X-Sequence-Number: 7550 On Fri, 2004-07-23 at 15:51, Jaime Casanova wrote: > Hi all, > > just as a question. > > There will be some day a feature that let you force > the planner to use an specific index, like oracle > does? > > Of course the planner is smart enough most times but > sometimes such an option would be usefull, don't you > think so? A planner that always made the right choice would be the most useful thing. After that, the ability to "push" the planner towards an index would be pretty nice. Adding features that make PostgreSQL more error prone (i.e. forcing particular index usage, etc.) and harder to drive but allow an expert to get what they want is kind of a dangerous road to tread.