From: Steinar H. Gunderson <sgunderson@bigfoot.com>
To: pgsql-performance@postgresql.org
Subject: Re: would number of fields in a table affect search-query time?
Date: Tue, 5 Oct 2004 01:34:36 +0200
Message-ID: <20041004233436.GB13394@uio.no> (raw)
In-Reply-To: <59b2d39b0410041627d405f39@mail.gmail.com>
References: <59b2d39b0410041627d405f39@mail.gmail.com>
On Mon, Oct 04, 2004 at 04:27:51PM -0700, Miles Keaton wrote:
> would the number of fields in a table significantly affect the
> search-query time?
More fields = larger records = fewer records per page = if you read in
everything, you'll need more I/O.
> I have this database table of items with LOTS of properties per-item,
> that takes a LONG time to search.
It's a bit hard to say anything without seeing your actual tables and
queries; I'd guess you either have a lot of matches or you're doing a
sequential scan.
You might want to normalize your tables, but again, it's hard to say anything
without seeing your actual data.
/* Steinar */
--
Homepage: http://www.sesse.net/
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: sgunderson@bigfoot.com
Subject: Re: would number of fields in a table affect search-query time?
In-Reply-To: <20041004233436.GB13394@uio.no>
* 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