From: Miles Keaton <mileskeaton@gmail.com>
To: pgsql-performance@postgresql.org
Subject: would number of fields in a table affect search-query time?
Date: Mon, 4 Oct 2004 16:27:51 -0700
Message-ID: <59b2d39b0410041627d405f39@mail.gmail.com> (raw)
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?
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: mileskeaton@gmail.com
Subject: Re: would number of fields in a table affect search-query time?
In-Reply-To: <59b2d39b0410041627d405f39@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox