From: Bruno Wolff III <bruno@wolff.to>
To: Rajesh Kumar Mallah <mallah@trade-india.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Effect of too many columns
Date: Mon, 12 Apr 2004 07:17:40 -0500
Message-ID: <20040412121740.GC20278@wolff.to> (raw)
In-Reply-To: <407A8369.9090205@trade-india.com>
References: <407A8369.9090205@trade-india.com>
On Mon, Apr 12, 2004 at 17:24:17 +0530,
Rajesh Kumar Mallah <mallah@trade-india.com> wrote:
>
> 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?
This is normally a bad idea. If you properly implement constraints in
what is effectively a materialized view, you might end up with a slower
system, depending on your mix of queries. (Generally updating will take
more resources.) So you probably want to test your new design under a
simulated normal load to see if it actually speeds things up in your
case before making the change.
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: bruno@wolff.to, mallah@trade-india.com
Subject: Re: Effect of too many columns
In-Reply-To: <20040412121740.GC20278@wolff.to>
* 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