pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron Johnson <ron.l.johnson@cox.net>
To: pgsql-performance@postgresql.org
Subject: Re: How number of columns affects performance
Date: 01 Aug 2003 14:19:20 -0500
Message-ID: <1059765560.22384.67.camel@haggis> (raw)
In-Reply-To: <200308011044.03493.josh@agliodbs.com>
References: <20030801115257.I92555@zoraida.natserv.net>
	<1059755687.7508.638.camel@haggis>
	<20030801130507.M93127@zoraida.natserv.net>
	<200308011044.03493.josh@agliodbs.com>

On Fri, 2003-08-01 at 12:44, Josh Berkus wrote:
> Francisco,
> 
> > Yes all fields belong to the same entity. I used 100 as an example it may
> > be something like 60 to 80 fields (there are two tables in question). I
> > don't formally do 3rd normal form, but for the most part I do most of
> > the general concepts of normalization.
> >
> > > If not, then good design says to split the table.
> 
> Actually, no, it doesn't.   If all 60-80 fields are unitary and required 
> characteristics of the row-entity, normalization says keep them in one table.

You snipped out too much, because that's exactly what I said...
Another way of writing it: only split the table if some of the fields
are not unitary to the entity.

> The only time NF would recommend splitting the table is for fields which are 
> frequenly NULL for reasons other than missing data entry.  For those, you'd 
> create a child table.  Although while this is good 4NF, it's impractical in 
> PostgreSQL, where queries with several LEFT OUTER JOINs tend to be very slow 
> indeed.

Good to know.

> My attitude toward these normalization vs. performance issues is consistenly 
> the same:  First, verify that you have a problem.   That is, build the 
> database with everything in one table (or with child tables for Nullable 
> fields, as above) and try to run your application.  If performance is 
> appalling, *then* take denormalization steps to improve it.

The OP was not talking about denormalizing ...

It was: will vertically partitioning a table increase performance.
And the answer is "sometimes",

-- 
+-----------------------------------------------------------------+
| Ron Johnson, Jr.        Home: ron.l.johnson@cox.net             |
| Jefferson, LA  USA                                              |
|                                                                 |
| "I'm not a vegetarian because I love animals, I'm a vegetarian  |
|  because I hate vegetables!"                                    |
|    unknown                                                      |
+-----------------------------------------------------------------+





view thread (9+ messages)  latest in thread

Message-ID: <1059765560.22384.67.camel@haggis>
Permalink:  ../1059765560.22384.67.camel@haggis/
Also on:    postgresql.org/message-id/1059765560.22384.67.camel@haggis

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: ron.l.johnson@cox.net
  Subject: Re: How number of columns affects performance
  In-Reply-To: <1059765560.22384.67.camel@haggis>
  References: <20030801115257.I92555@zoraida.natserv.net> <1059755687.7508.638.camel@haggis> <20030801130507.M93127@zoraida.natserv.net> <200308011044.03493.josh@agliodbs.com> <1059765560.22384.67.camel@haggis>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox