X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 8C9B5329F40 for ; Tue, 5 Oct 2004 03:07:27 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 33280-01 for ; Tue, 5 Oct 2004 02:07:18 +0000 (GMT) Received: from davinci.ethosmedia.com (server226.ethosmedia.com [209.128.84.226]) by svr1.postgresql.org (Postfix) with ESMTP id 7CF0D329D20 for ; Tue, 5 Oct 2004 03:07:20 +0100 (BST) Received: from [63.195.55.98] (account josh@agliodbs.com HELO spooky) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 6458521; Mon, 04 Oct 2004 19:08:41 -0700 From: Josh Berkus Organization: Aglio Database Solutions To: Miles Keaton Subject: Re: would number of fields in a table affect search-query time? Date: Mon, 4 Oct 2004 19:06:33 -0700 User-Agent: KMail/1.6.2 Cc: pgsql-performance@postgresql.org References: <59b2d39b0410041627d405f39@mail.gmail.com> In-Reply-To: <59b2d39b0410041627d405f39@mail.gmail.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200410041906.33483.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200410/39 X-Sequence-Number: 8515 Miles, > would the number of fields in a table significantly affect the > search-query time? Yes. In addition to the issues mentioned previously, there is the issue of criteria; an OR query on 8 fields is going to take longer to filter than an OR query on 2 fields. Anyway, I think maybe you should tell us more about your database design. Often the fastest solution involves a more sophisticated approach toward querying your tables. -- Josh Berkus Aglio Database Solutions San Francisco