pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: Alexander Priem <ap@cict.nl>
To: pgsql-performance@postgresql.org
Subject: Re: Many fields in one table or many tables?
Date: Thu, 18 Sep 2003 10:27:12 -0700
Message-ID: <200309181027.12195.josh@agliodbs.com> (raw)
In-Reply-To: <008901c37dbc$b3615550$b696a8c0@APR>
References: <20399973.1063861169740.JavaMail.root@rowlf.psp.pas.earthlink.net>
	<008901c37dbc$b3615550$b696a8c0@APR>

Alexander,

> I am in the process of creating a database design in which LOTS of data
> need to be modelled.
>
> For instance, I need to store data about products. Every product has LOTS
> of properties, well over a hundred.
<snip>
> Do any of you know if and how PostgreSQL would prefer one approach over the
> other?

Queston 1:  Do all products have all of these properties, or do some/many/most 
not have some properties?   If the answer is the former, then a single table, 
however broad, is the logical construct.  If the latter, than several tables 
makes more sense: why create NULL columns for stuff you could just leave out?

Question 2: Is it true that some properties will be updated *much* (100x) more 
frequently than others?   If so, it would make sense from a 
performance/postgresql standpoint to isolate those properties to related 
table(s).  Keep in mind that this recommendation is strictly performance 
related, and is not necessarily the best relational design.

Suggestion 3: There was an issue in 7.3 with table rows which are overly broad 
-- some problems with PSQL, I believe.   It would be worth searching for, as 
I cannot remember what the limit is where problems occurred.

-- 
Josh Berkus
Aglio Database Solutions
San Francisco



view thread (3+ messages)  latest in thread

Message-ID: <200309181027.12195.josh@agliodbs.com>
Permalink:  ../200309181027.12195.josh@agliodbs.com/
Also on:    postgresql.org/message-id/200309181027.12195.josh@agliodbs.com

 · 

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: josh@agliodbs.com, ap@cict.nl
  Subject: Re: Many fields in one table or many tables?
  In-Reply-To: <200309181027.12195.josh@agliodbs.com>
  References: <20399973.1063861169740.JavaMail.root@rowlf.psp.pas.earthlink.net> <008901c37dbc$b3615550$b696a8c0@APR> <200309181027.12195.josh@agliodbs.com>

* 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