Skip site navigation (1) Skip section navigation (2)

Having MANY MANY empty columns in database

From: "sathiya psql" <sathiya(dot)psql(at)gmail(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Having MANY MANY empty columns in database
Date: 2008-03-22 04:10:02
Message-ID: f966c2ee0803212110n2d84585eqf5d9bf67cdba0898@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
Hi All,

I want some clarification in the following,

In a database which we are having we have nearly 100 tables, and in 75% of
the tables we have 6 columns ( INT ) as standard columns. What is standard
columns, if you create a table in this database you should have some default
6 columns in there they should maintain
    1. who is the owner of that read
    2. when it is added
    3. who is updating the record
    4. when it is updated .... and other columns....

But many of the users are not doing anything with those columns, they are
all empty always....

Say in that 75 % of tables, 60 % table contains nearly 1000 records
always...

and other 10% of tables contains less than 10000 records

and 5% of table contain records nealy 5 lakh.....

What i need is???

If you drop those columns we will gain any performance or not.....
Definitely i know having that columns is not useful, but i want some
clarification that having empty columns will make performance degradation or
not....


Am using Debian, and having 1 GB RAM...
I want this informations in both postgres 7.4 and 8.1 ( don't ask me to use
8.3 please, i want info in 7.4 and 8.1 )...


Regards
SathiyaMoorthy

Responses

pgsql-performance by date

Next:From: Craig RingerDate: 2008-03-22 08:24:17
Subject: Re: Having MANY MANY empty columns in database
Previous:From: Bruce MomjianDate: 2008-03-22 01:44:29
Subject: Re: Linux/PostgreSQL scalability issue - problem with 8 cores

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group