From sebyte at smolny.plus.com  Tue Mar  1 12:29:03 2011
From: sebyte at smolny.plus.com (Sebastian Tennant)
Date: Tue, 01 Mar 2011 12:29:03 +0000
Subject: [postmodern-devel] How to remove trailing spaces?
References: <AANLkTikVN1uA297Od7+=qvcXEGDjk4z-ye+2rPih7Pr3@mail.gmail.com>
	<AANLkTikq1YzXEN1HtVrfrfLo5eAjB9A5YwZZ_0BtNdKU@mail.gmail.com>
	<AANLkTinXBWn-CjZAbTD03reG8irUHLHctHKUeriLwAyA@mail.gmail.com>
	<AANLkTimJf1YxaDBSg97nkiCEZN-AngMXzkee+UULp7TS@mail.gmail.com>
Message-ID: <4o7nf2i8.fsf@chimera.gnukahvesi.net>

Quoth Marijn Haverbeke <marijnh at gmail.com>:
>> I meant that I thougth that postgresql could be faster with fixed
>> lenght fields, not postmodern, sorry... :-D
>
> Benchmark this, before you make life hard for yourself. I seem to
> remember an expert telling me that fixed char columns are rarely
> useful anymore.

 http://www.postgresql.org/docs/8.3/interactive/datatype-character.html

 "There are no performance differences between [character, character varying &
  text data types], apart from increased storage size when using the
  blank-padded type, and a few extra cycles to check the length when storing
  into a length-constrained column.  While `character(N)' has performance
  advantages in some other database systems, it has no such advantages in
  PostgreSQL.  In most situations `text' or `character varying' should be used
  instead."

Seb
-- 
Emacs' AlsaPlayer - Music Without Jolts
Lightweight, full-featured and mindful of your idyllic happiness.
http://home.gna.org/eap