OID vs overall system performances on high load databases.

From: "Eric Lauzon" <eric(dot)lauzon(at)abovesecurity(dot)com>
To: <pgsql-performance(at)postgresql(dot)org>
Subject: OID vs overall system performances on high load databases.
Date: 2005-05-27 17:05:57
Message-ID: F7B73864DD39FA40B6C56B3CE0D4D1CB634477@asdc003.abovesecurite.lan
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

What are the effect of having a table with arround 500 insert/update/delete on two to eight table in a time frame of 2 minutes 24/24h, when you have oid enabled versus the same setup when you dont have oid?

That deployment is done on a postgres with 8 to 9 databases, each having those 2 to 8 high load tables with oid enabled.

Would the oid colum slow down table scan when you have over 20 millions row?

Would the cost of maintaining the oid column inside thoses high load tables when there is no oid reference used for data seeking costy for postgres ressources!?

Eric Lauzon
[Recherche & Développement]
Above Sécurité / Above Security
Tél : (450) 430-8166
Fax : (450) 430-1858

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Jeffrey Tenny 2005-05-27 21:28:01 Redundant indexes?
Previous Message Josh Close 2005-05-27 15:00:23 Re: slow queries, possibly disk io