X-Original-To: pgsql-sql@postgresql.org
Received: from localhost (postgresql.org [64.49.215.8])
	by postgresql.org (Postfix) with ESMTP id 438D5475D64
	for <pgsql-sql@postgresql.org>; Fri, 28 Feb 2003 20:23:49 -0500 (EST)
Received: from postgresql.org ([64.49.215.8])
	by localhost (postgresql.org [64.49.215.8:10024]) (amavisd-new) with
	SMTP id 22234-02 for <pgsql-sql@postgresql.org>;
	Fri, 28 Feb 2003 20:23:47 -0500 (EST)
Received: from polaris.pinpointresearch.com (66-7-238-176.cust.telepacific.net
	[66.7.238.176]) by postgresql.org (Postfix) with ESMTP id CC6CA475F31
	for <pgsql-sql@postgresql.org>; Fri, 28 Feb 2003 20:16:39 -0500 (EST)
Received: from there (66-7-238-179.cust.telepacific.net [66.7.238.179])
	by polaris.pinpointresearch.com (Postfix) with SMTP
	id D1C57103C9; Fri, 28 Feb 2003 17:16:42 -0800 (PST)
Content-Type: text/plain;
  charset="iso-8859-1"
From: Steve Crawford <scrawford@pinpointresearch.com>
Organization: Pinpoint Research
To: "Montrone, Marc -- 7183" <marc.montrone@novastar1.com>,
	"'pgsql-sql@postgresql.org'" <pgsql-sql@postgresql.org>
Subject: Re: Optimizing
Date: Fri, 28 Feb 2003 17:16:42 -0800
X-Mailer: KMail [version 1.3.1]
References: <6F92EBF93563D411A42200508BD97A9A05645C2A@KCNT02B>
In-Reply-To: <6F92EBF93563D411A42200508BD97A9A05645C2A@KCNT02B>
MIME-Version: 1.0
Message-Id: <20030301011642.D1C57103C9@polaris.pinpointresearch.com>
Content-Transfer-Encoding: quoted-printable
X-Virus-Scanned: by amavisd-new
X-Archive-Number: 200302/640
X-Sequence-Number: 12038

That should be virtually instant.

First, the usual suspects: have you run "vacuum analyze" on your table? If=
=20
not, do it and try again.

If so, please show us your table structure, index, and query - just fire up=
=20
psql and run "\d yourtablename" and "explain <your query>" and send it to u=
s.

Cheers,
Steve

On Friday 28 February 2003 7:26 am, Montrone, Marc -- 7183 wrote:
> Please advise how I can improve performance of query searching for
> telephone numbers. I have a table with over a million records of phone
> numbers in a single indexed field. To find one phone number takes nearly =
20
> seconds. Aside from hardware upgrades, how can I improve the performance =
of
> this query? Thank you in advance.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org