pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
How to split very long tables?
2+ messages / 2 participants
[nested] [flat]

* How to split very long tables?
@ 1998-07-06 12:53  Stuart Rison <stuart@ludwig.ucl.ac.uk>
  0 siblings, 1 reply; 2+ messages in thread

From: Stuart Rison @ 1998-07-06 12:53 UTC (permalink / raw)
  To: pgsql-sql

Dear All,

I am using postgreSQL to matain a database of breast cancer patient data.
I have create a hugely long (i.e. many columns) table and it is becoming
unmanageable (I can't get the whole of it on screen, some queries appear to
exceed the maximum string length etc.)

How do you 'split' a long table without adding excessive redundency?  Is it
OK to just cut the table up and use the same primary key?

I would be grateful for any comments/suggestions.

Cheers,

Stuart.

PS.  could you please cc me a copy of your posting(s).


+-------------------------+--------------------------------------+
| Stuart Rison            | Ludwig Institute for Cancer Research |
| Tel. (0171) 878 4041    | Courtauld Building                   |
| Fax. (0171) 878 4040    | 91 Riding House Street               |
+-------------------------+ London, W1P 8BT                      |
| stuart@ludwig.ucl.ac.uk | UNITED KINGDOM.                      |
+-------------------------+--------------------------------------+





^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: [SQL] How to split very long tables?
@ 1998-07-06 13:59  Brett W. McCoy <bmccoy@lan2wan.com>
  parent: Stuart Rison <stuart@ludwig.ucl.ac.uk>
  0 siblings, 0 replies; 2+ messages in thread

From: Brett W. McCoy @ 1998-07-06 13:59 UTC (permalink / raw)
  To: Stuart Rison <stuart@ludwig.ucl.ac.uk>; +Cc: pgsql-sql

On Mon, 6 Jul 1998, Stuart Rison wrote:

> I am using postgreSQL to matain a database of breast cancer patient data.
> I have create a hugely long (i.e. many columns) table and it is becoming
> unmanageable (I can't get the whole of it on screen, some queries appear to
> exceed the maximum string length etc.)
> 
> How do you 'split' a long table without adding excessive redundency?  Is it
> OK to just cut the table up and use the same primary key?

Is it possible to normalize your table, and build up a set of relations 
between the tables?  If not, you may want to break your tables down into 
years (I do this for some data), and just treat each year as a discrete 
set.  You may be able to do a join between views to use the tables as a 
single set of data, but then you are right back where you started with 
too much data.  How many rows are in this table?

Brett W. McCoy           
                                         http://www.lan2wan.com/~bmccoy
-----------------------------------------------------------------------
"The Number of UNIX installations has grown to 10, with more expected."
   -- The UNIX Programmer's Manual, 2nd Edition, June, 1972




^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~1998-07-06 13:59 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1998-07-06 12:53 How to split very long tables? Stuart Rison <stuart@ludwig.ucl.ac.uk>
1998-07-06 13:59 ` Brett W. McCoy <bmccoy@lan2wan.com>

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