From: Francisco Reyes <lists@natserv.com>
To: PostgreSQL performance <pgsql-performance@postgresql.org>
Subject: How number of columns affects performance
Date: Fri, 1 Aug 2003 12:08:18 -0400 (EDT)
Message-ID: <20030801115257.I92555@zoraida.natserv.net> (raw)
If a table which will be heavily used has numerous fields, yet only a
handfull of them will be used heavily, would it make sense performance wise to split it?
Example
Table 1
Field 1
....
Field 100
Table 2
References Field 1 of table1
.....
Table n
References Field 1 of table 1
So table 1 basically will be referenced by many tables and most of the
time only a handfull of fields of table 1 are needed. Don't have exact
numbers, but let's say that more than 60% of queries to table 1 queries
only use 20 fields or less.
If I split Table 1 then the second table will basically be a 1 to 1 to
Table 1.
I have this simmilar scenario for two tables. One is close to 1 Million
records and the other is about 300,000 records.
Programming wise it is much easier to only have one table, but I am just
concerned about performance.
Most access to these tables will be indexed with some occassional
sequential scans. Number of concurrent users now is probably 10 or less.
Expect to grow to 20+ concurrent connections. Will this be more of an
issue if I had hundreds/thousands of users?
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: lists@natserv.com
Subject: Re: How number of columns affects performance
In-Reply-To: <20030801115257.I92555@zoraida.natserv.net>
References: <20030801115257.I92555@zoraida.natserv.net>
* 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