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 4BAD132A2B4 for ; Tue, 5 Oct 2004 00:32:16 +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 98136-10 for ; Mon, 4 Oct 2004 23:32:09 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id E5F0B329E01 for ; Tue, 5 Oct 2004 00:32:10 +0100 (BST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id i94NW93t007325; Mon, 4 Oct 2004 19:32:10 -0400 (EDT) To: Miles Keaton Cc: pgsql-performance@postgresql.org Subject: Re: would number of fields in a table affect search-query time? In-reply-to: <59b2d39b0410041627d405f39@mail.gmail.com> References: <59b2d39b0410041627d405f39@mail.gmail.com> Comments: In-reply-to Miles Keaton message dated "Mon, 04 Oct 2004 16:27:51 -0700" Date: Mon, 04 Oct 2004 19:32:09 -0400 Message-ID: <7324.1096932729@sss.pgh.pa.us> From: Tom Lane 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/37 X-Sequence-Number: 8513 Miles Keaton writes: > What surprised me the most is that the subset, even in the original > database, gave search results MUCH faster than the full table! The subset table's going to be physically much smaller, so it could just be that this reflects smaller I/O load. Hard to tell without a lot more detail about what case you were testing. regards, tom lane