> I think I understand your point, however it would be very laborious after
> you do all development to find out you need to de-normalize.

Not terribly.   Views and Rules are good for this.

> On your experience at which point it would actually help to do this
> de-normalization in PostgreSQL? I know there are numerous factors ,but any
> feedback based on previous experiences would help.

My experience?   If you're running on good hardware, it's completely 
unnecessary to vertically partition the table.   The only thing I'd do would 
be to look for columns which are frequently NULL and can be grouped together, 
and spin those off into a sub-table.   That is, if you have 4 columns which 
are generally either all null or all filled, and are all null for 70% of 
records then those 4 could make a nice child table.

-Josh Berkus

______AGLIO DATABASE SOLUTIONS___________________________
                                        Josh Berkus
   Complete information technology      [EMAIL PROTECTED]
    and data management solutions       (415) 565-7293
   for law firms, small businesses       fax 621-2533
    and non-profit organizations.       San Francisco

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match

Reply via email to