X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 54E6AD1CCB7 for ; Mon, 12 Apr 2004 08:52:22 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 57198-06 for ; Mon, 12 Apr 2004 08:52:23 -0300 (ADT) Received: from trade-india.com (unknown [61.16.154.82]) by svr1.postgresql.org (Postfix) with SMTP id EFB68D1DC69 for ; Mon, 12 Apr 2004 08:52:17 -0300 (ADT) Received: (qmail 15532 invoked from network); 12 Apr 2004 11:40:01 -0000 Received: from valium.trade-india-local.com (HELO trade-india.com) (192.168.0.72) by system66.trade-india-local.com with SMTP; 12 Apr 2004 11:40:01 -0000 Message-ID: <407A8369.9090205@trade-india.com> Date: Mon, 12 Apr 2004 17:24:17 +0530 From: Rajesh Kumar Mallah Organization: Infocom Network Limited User-Agent: Mozilla Thunderbird 0.5 (X11/20040208) X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: Effect of too many columns Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/127 X-Sequence-Number: 6427 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.