From: Rajesh Kumar Mallah <mallah@trade-india.com>
To: pgsql-performance@postgresql.org
Subject: Effect of too many columns
Date: Mon, 12 Apr 2004 17:24:17 +0530
Message-ID: <407A8369.9090205@trade-india.com> (raw)
Greetings,
Is there any performance penalty of having too many columns in
a table in terms of read and write speeds.
To order to keep operational queries simple (avoid joins) we plan to
add columns in the main customer dimension table.
Adding more columns also means increase in concurrency in the table
as more and more applications will access the same table.
Any ideas if its better to split the table application wise or is it ok?
Regds
mallah.
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: mallah@trade-india.com
Subject: Re: Effect of too many columns
In-Reply-To: <407A8369.9090205@trade-india.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