Received: from megazone.bigpanda.com (megazone.bigpanda.com [63.150.15.178]) by postgresql.org (Postfix) with ESMTP id 134FD4767C2 for ; Fri, 22 Feb 2002 11:12:58 -0500 (EST) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id DF995D600; Fri, 22 Feb 2002 08:13:02 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id D51045BF9; Fri, 22 Feb 2002 08:13:02 -0800 (PST) Date: Fri, 22 Feb 2002 08:13:02 -0800 (PST) From: Stephan Szabo To: "Samuel J. Sutjiono" Cc: Subject: Re: How does Index Scan get used In-Reply-To: <018a01c1bbaf$befb84b0$110a010a@headquarters.wcgroup.com> Message-ID: <20020222081158.U35057-100000@megazone23.bigpanda.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200202/317 X-Sequence-Number: 6739 On Fri, 22 Feb 2002, Samuel J. Sutjiono wrote: > I tried an Index Scan but I kept on getting Seq Scan. Do you know why > ? What do I need to do to get my query to use index scan (I tried to > turn it on by doing SET ENABLE_indexscan = on; but it didn't work) > > create table test (test_col text); > create index test_index on test (test_col); > insert into test values ('abc.xyz'); > insert into test values ('abcxyz'); > insert into test values ('abc/xyz'); > > explain select * from test where test_col like 'abc/%'; > > NOTICE: QUERY PLAN: > > Seq Scan on test (cost=0.00..22.50 rows=10 width=12) > > Another question: > Does Regex (~*) or like use table scan ? It may, but IIRC only if you're running in 'C' locale (the rule being used to make it indexable doesn't necessarily work in other locales).