pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Mag Gam <magawake@gmail.com>
To: Jonah H. Harris <jonah.harris@gmail.com>
Cc: Jean-David Beyer <jeandavid8@verizon.net>
Cc: pgsql-sql@postgresql.org
Subject: Re: Curious about wide tables.
Date: Sun, 27 Apr 2008 12:14:49 -0400
Message-ID: <1cbd6f830804270914r1e666210n987b0798faf59656@mail.gmail.com> (raw)
In-Reply-To: <36e682920804270906i7b5c5ab9v4e06688df85f810@mail.gmail.com>
References: <48147917.8000108@verizon.net>
	<36e682920804270906i7b5c5ab9v4e06688df85f810@mail.gmail.com>

Any chance this could be a view?


On Sun, Apr 27, 2008 at 12:06 PM, Jonah H. Harris <jonah.harris@gmail.com>
wrote:

> On Sun, Apr 27, 2008 at 9:01 AM, Jean-David Beyer
> <jeandavid8@verizon.net> wrote:
> > In another thread, the O.P. had a question about a large table with over
> 100
> >  columns. Is this usual? Whenever I make a database, which is not often,
> it
> >  ends up with tables that rarely have over to columns, and usually less
> than
> >  that. When normalized, my tables rarely get very wide.
>
> Yes, even in several well-normalized schemas I've seen tables with
> over 250 columns.
>
> >  Without criticising the O.P., since I know nothing about his
> application, I
> >  am curious how it comes about that such a wide table is justified.
>
> The few applications I've seen with large tables were an insurance
> system, an manufacturing system, and a sensor-recording system (which
> was more optimal to store as an attribute-per-instance-of-time than a
> separate tuple containing the time, sensor, and value).
>
> --
> Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
> EnterpriseDB Corporation | fax: 732.331.1301
> 499 Thornall Street, 2nd Floor | jonah.harris@enterprisedb.com
> Edison, NJ 08837 | http://www.enterprisedb.com/
>
> --
> Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-sql
>

view thread (5+ messages)  latest in thread

Message-ID: <1cbd6f830804270914r1e666210n987b0798faf59656@mail.gmail.com>
Permalink:  ../1cbd6f830804270914r1e666210n987b0798faf59656@mail.gmail.com/
Also on:    postgresql.org/message-id/1cbd6f830804270914r1e666210n987b0798faf59656@mail.gmail.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 using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: magawake@gmail.com, jonah.harris@gmail.com, jeandavid8@verizon.net
  Subject: Re: Curious about wide tables.
  In-Reply-To: <1cbd6f830804270914r1e666210n987b0798faf59656@mail.gmail.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