pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: David C Hartwig Jr <daybee@bellatlantic.net>
To: Michael McCarthy <michael@tcsi.com>
Cc: pgsql-sql@postgreSQL.org, Hemant Yevale <hemant@tcsi.com>
Cc: Savyasachi Jog <jog@tcsi.com>
Subject: Re: [SQL] problem with OR'ed AND queriess
Date: Tue, 21 Dec 1999 21:47:23 -0500
Message-ID: <38603BBB.E93C561C@bellatlantic.net> (raw)
References: <Pine.GSO.3.96.991221151143.9161K-100000@sanmarino.tcsi.com>

Michael McCarthy wrote:

> Hello David:
>
> Thanks for the quick reply; it means a lot to me.
>
> I tried "SET ksqo TO 'on'", and it works fine for my problem query; it
> allowed 570 key sets to be resolved in 2 seconds, which is a big step
> forward.
>
> I am writing a layer which makes postgres one RDBMS (of several) which can
> support a generic object persistence framework. The use of "SET ksqo TO
> 'on'" is a postgres implementation detail which applications using the
> framework will not be aware of. I am faced with the problem of whether or
> not to use "SET ksqo TO 'on'" for all queries, or find some criteria for
> turning it on and off.
>
> 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?

The qualification is strict so that it can be left on without breaking other queries.   Most MS ODBC users
use it all the time; I have yet to hear of it causing any problems.

>
>
>
> > There is a work around feature that works for queries that gererate a parse tree similar to yours.
> > ODBC tools generate these kinds of queries all the time.    Keyset queries.   To acivate the
> > feature:    SET ksqo TO 'on';    It rewrites the parse tree into a series of UNIONs.   Not optimal but
> > it works for rectangular where clauses.   (n ANDs) x  (m ORs)
> >
> > --   Here is an example using a 3 part key
> >      select ... from foo where
> >          (v1 = "?" AND v2 = "?" AND v3 ="?") OR        -- line 1
> >          (v1 = "?" AND v2 = "?" AND v3 ="?") OR        -- line 2
> >                  ...
> >          (v1 = "?" AND v2 = "?" AND v3 ="?") OR        --  line 9
> >          (v1 = "?" AND v2 = "?" AND v3 ="?");              --  line 10
> >      --  The question marks are replaced with the constant key values
>
> ************




view thread (7+ messages)  latest in thread

Message-ID: <38603BBB.E93C561C@bellatlantic.net>
Permalink:  ../38603BBB.E93C561C@bellatlantic.net/
Also on:    postgresql.org/message-id/38603BBB.E93C561C@bellatlantic.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: daybee@bellatlantic.net, michael@tcsi.com, hemant@tcsi.com, jog@tcsi.com
  Subject: Re: [SQL] problem with OR'ed AND queriess
  In-Reply-To: <38603BBB.E93C561C@bellatlantic.net>
  References: <Pine.GSO.3.96.991221151143.9161K-100000@sanmarino.tcsi.com> <38603BBB.E93C561C@bellatlantic.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox