PGSQL GENERAL 24 USING INHERITANCE IN PRODUCTION APPLICATION
From: ljw1001@no-spam (Larry White)
Subject: using inheritance in production application.
Date: Thu, 9 Dec 2004 15:21:53 -0500


How 'ready for prime-time' is the table inheritance feature? I've seen some postings about particular issues (lack of full FK support,
for example), but would like to get an overall sense of the stability and robustness of the feature.

Also, is there a performance hit in using inheritance? For example if I have a sub-table that adds a couple of columns to a base table,
would it be slower to query that structure than it would to represent the extra columns as a separate table that would be joined with the base table?

thanks for your help.

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster









From: pgman@no-spam (Bruce Momjian)
Subject: Re: using inheritance in production application.
Date: Sun, 12 Dec 2004 23:33:58 -0500 (EST)

Larry White wrote:
> How 'ready for prime-time' is the table inheritance feature? I've > seen some postings about particular issues (lack of full FK support,
> for example), but would like to get an overall sense of the stability > and robustness of the feature.
> > Also, is there a performance hit in using inheritance? For example if > I have a sub-table that adds a couple of columns to a base table,
> would it be slower to query that structure than it would to represent > the extra columns as a separate table that would be joined with the > base table?

All inheritance problems are mentioned on the TODO list, and none are performance-related. They all revolve around the inability of an index to span multiple tables.

-- Bruce Momjian | http://candle.pha.pa.us pgman@no-spam | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@no-spam