Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id XAA19346 for ; Tue, 21 Dec 1999 23:16:12 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id XAA14564; Tue, 21 Dec 1999 23:13:52 -0500 (EST) To: Michael McCarthy cc: David C Hartwig Jr , pgsql-sql@postgreSQL.org, Hemant Yevale , Savyasachi Jog Subject: Re: [SQL] problem with OR'ed AND queriess In-reply-to: References: Comments: In-reply-to Michael McCarthy message dated "Tue, 21 Dec 1999 15:33:29 -0800" Date: Tue, 21 Dec 1999 23:13:52 -0500 Message-ID: <14561.945836032@sss.pgh.pa.us> From: Tom Lane Michael McCarthy writes: > A quick examination of backend/optimizer/prep/prepkeyset.c shows me that > there is some qualification of a query for keyset optimization; is there > any reason why I should not always set ksqo on? If it seems to win more often than not for your query mix, go for it. ksqo is a hack that I'm hoping to eliminate in the next release or three. But right now, it's a mighty useful hack if you do a lot of OR-of-AND queries... regards, tom lane