X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.193]) by svr1.postgresql.org (Postfix) with ESMTP id A39E730E32B for ; Mon, 16 Jun 2003 19:53:06 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr1.postgresql.org [64.117.224.193]) (amavisd-new, port 10024) with ESMTP id 83390-03 for ; Mon, 16 Jun 2003 16:52:55 -0300 (ADT) Received: from wolff.to (wolff.to [66.93.249.74]) by svr1.postgresql.org (Postfix) with SMTP id 05EE330E35D for ; Mon, 16 Jun 2003 16:52:55 -0300 (ADT) Received: (qmail 9263 invoked by uid 500); 16 Jun 2003 19:55:51 -0000 Date: Mon, 16 Jun 2003 14:55:51 -0500 From: Bruno Wolff III To: Tomasz Myrta Cc: pgsql-performance@postgresql.org Subject: Re: sequential scans on few columns tables Message-ID: <20030616195551.GB8871@wolff.to> Mail-Followup-To: Tomasz Myrta , pgsql-performance@postgresql.org References: <3EEE1F54.3030507@klaster.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3EEE1F54.3030507@klaster.net> User-Agent: Mutt/1.5.4i X-Archive-Number: 200306/96 X-Sequence-Number: 2180 On Mon, Jun 16, 2003 at 21:49:40 +0200, Tomasz Myrta wrote: > Hi > Recently I was wondering about tables difficult to index. Example - > queries with "ilike" where clauses. Without additional contrib modules > the only way to search such tables is sequential scan (am I right?) You might be able to use a functional index depending on exactly what your search patterns are like.