From: | "Kris" <kkiger(at)depauw(dot)edu> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Speed & Memory Management |
Date: | 2003-03-31 22:08:26 |
Message-ID: | b6ae8p$30p7$1@news.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hello all. I am designing a database that will could potentially grow to
have millions of tuples associated with it. My thought is that because I
will likely have many updates/inserts/deletes occurring I should set each
column that requires text to a static ammount (ie using char(30) instead of
text). However, this looks to be a double edged sword, since selecting from
the db is my largest concern (with updates a very close second). When I
pull these values back out of the db, it seems I am going to have to trim
each returned value (when I pull a ten character string out of this field,
it returns the 10 char string as well as 20 whitespaces.). I am trying to
assign a weight to each of these scenarios and figure out which is the
lesser of the two evils. If anyone has a suggestion of how I may circumvent
this issue or which possibility may work best, it would be greatly
appreciated. Thanks
Kris
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-04-01 03:42:44 | Re: lost tables |
Previous Message | Tom Lane | 2003-03-31 21:43:44 | Re: [ADMIN] Can't connect to my postgresql |