pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Kris <kkiger@depauw.edu>
To: pgsql-admin@postgresql.org
Subject: Speed & Memory Management
Date: Mon, 31 Mar 2003 17:08:26 -0500
Message-ID: <b6ae8p$30p7$1@news.hub.org> (raw)

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




view thread (14+ messages)  latest in thread

Message-ID: <b6ae8p$30p7$1@news.hub.org>
Permalink:  ../b6ae8p$30p7$1@news.hub.org/
Also on:    postgresql.org/message-id/b6ae8p$30p7$1@news.hub.org

 · 

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-admin@postgresql.org
  Cc: kkiger@depauw.edu
  Subject: Re: Speed & Memory Management
  In-Reply-To: <b6ae8p$30p7$1@news.hub.org>
  References: <b6ae8p$30p7$1@news.hub.org>

* 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