Table inheritance and performance

From: Jean-Christian Imbeault <jc(at)mega-bucks(dot)co(dot)jp>
To: pgsql-general(at)postgresql(dot)org
Subject: Table inheritance and performance
Date: 2003-07-28 02:00:30
Message-ID: 3F2483BE.6070400@mega-bucks.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I'm in the design stage of a database and I am thinking of using table
inheritance for the first time. However I've been wondering if table
inheritance would be all that useful and what, if any, performance
penalties there might be.

For example, say I have a parent table FRUITS and two children, APPLES
and ORANGES, where the APPPLES and ORANGES tables are identical.
Performance-wise would it be any different from having just one table,
FRUITS, and a column TYPE which would be a foreign key into a types
table (1 = APPLE, 2 = ORANGE, etc ...). Would using inheritance in this
case be a performance hit compared to a simple type column with lookup
table? Or would there be no penalty for using inheritance?

Thanks,

Jean-Christian Imbeault

Browse pgsql-general by date

  From Date Subject
Next Message Weiping He 2003-07-28 02:06:58 Re: unicode char order
Previous Message LitelWang 2003-07-28 01:00:58 unicode char order