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 A7E7B329E01 for ; Tue, 5 Oct 2004 00:28:01 +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 98525-04 for ; Mon, 4 Oct 2004 23:27:55 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.193]) by svr1.postgresql.org (Postfix) with ESMTP id 7ADC1329D9F for ; Tue, 5 Oct 2004 00:27:56 +0100 (BST) Received: by mproxy.gmail.com with SMTP id 73so3431920rnk for ; Mon, 04 Oct 2004 16:27:52 -0700 (PDT) Received: by 10.38.208.76 with SMTP id f76mr2869849rng; Mon, 04 Oct 2004 16:27:51 -0700 (PDT) Received: by 10.38.151.40 with HTTP; Mon, 4 Oct 2004 16:27:51 -0700 (PDT) Message-ID: <59b2d39b0410041627d405f39@mail.gmail.com> Date: Mon, 4 Oct 2004 16:27:51 -0700 From: Miles Keaton Reply-To: Miles Keaton To: pgsql-performance@postgresql.org Subject: would number of fields in a table affect search-query time? Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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/36 X-Sequence-Number: 8512 would the number of fields in a table significantly affect the search-query time? (meaning: less fields = much quicker response?) I have this database table of items with LOTS of properties per-item, that takes a LONG time to search. So as I was benchmarking it against SQLite, MySQL and some others, I exported just a few fields for testing, into all three databases. What surprised me the most is that the subset, even in the original database, gave search results MUCH faster than the full table! I know I'm being vague, but does anyone know if this is just common knowledge ("duh! of course!") or if I should be looking at is as a problem to fix?