From: "Keith Worthington" <keithw@narrowpathinc.com>
To: "PostgreSQL SQL" <pgsql-sql@postgresql.org>
Cc: "Sean Davis" <sdavis2@mail.nih.gov>,
	"Scott Marlowe" <smarlowe@g2switchworks.com>
Reply-To: KeithW@narrowpathinc.com
Subject: Re: More efficient OR
Date: Wed, 16 Feb 2005 11:35:30 -0500
Message-Id: <20050216162747.M40986@narrowpathinc.com>
In-Reply-To: <BFC3420B-8036-11D9-B22E-000D933565E8@mail.nih.gov>
References: <20050216155901.M41773@narrowpathinc.com>
	<BFC3420B-8036-11D9-B22E-000D933565E8@mail.nih.gov>
MIME-Version: 1.0
Content-Type: text/plain;
	charset=iso-8859-1

> > Hi All,
> >
> > In several of my SQL statements I have to use a WHERE clause
> > that contains mutiple ORs.  i.e.
> >
> > WHERE column1 = 'A' OR
> >       column1 = 'B' OR
> >       column1 = 'C'
> >
> > Is there a more efficient SQL statement that accomplishes the
> > same limiting functionality?
> >
> > Kind Regards,
> > Keith
> >
>
> Scott wrote:
> The in() construct is (nowadays) basically the same as
> ORing multiple columns;
> 
> where column1 in ('A','B','C') 
> 
> 
> Sean Davis wrote
> Could 'in' or 'between' do what you want?  I know that using 'in'
> is equivalent to what you have below.  Could 'between' be more 
> efficient--you could do explain analyze on various options to see 
> what the actual plan would be.
> 
> Sean

Thanks Scott and Sean for the post.

It sounds like IN will save some typing and code space but not decrease the
execution time.

BETWEEN won't work for my real life query because the limiting values are
quite disparate.

Kind Regards,
Keith