From: Murthy Kambhampaty <murthy.kambhampaty@goeci.com>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: pgsql-admin@postgresql.org
Subject: Re: Speed & Memory Management
Date: Wed, 2 Apr 2003 13:00:28 -0500
Message-ID: <2D92FEBFD3BE1346A6C397223A8DD3FC0921C3@THOR.goeci.com> (raw)
This, and the message from Tom Lane, seem inconsistent with the
documentation re "Character Types"
(http://developer.postgresql.org/docs/postgres/datatype-character.html)
which says:
"Tip: There are no performance differences between these three types, apart
from the increased storage size when using the blank-padded type."
-----Original Message-----
From: Peter Eisentraut [mailto:peter_e@gmx.net]
Sent: Tuesday, April 01, 2003 16:42
To: Kris
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Speed & Memory Management
Kris writes:
> 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).
That would buy you absolutely nothing. char() is not faster than text.
Instead you would make everything slower because the system would
constantly have to pad and trim your values and it would bloat the storage
with the extra spaces.
--
Peter Eisentraut peter_e@gmx.net
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
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: murthy.kambhampaty@goeci.com, peter_e@gmx.net
Subject: Re: Speed & Memory Management
In-Reply-To: <2D92FEBFD3BE1346A6C397223A8DD3FC0921C3@THOR.goeci.com>
References: <2D92FEBFD3BE1346A6C397223A8DD3FC0921C3@THOR.goeci.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