From: chrisj <chrisj.wood@sympatico.ca>
To: pgsql-performance@postgresql.org
Subject: seeking advise on char vs text or varchar in search table
Date: Fri, 20 Apr 2007 07:23:58 -0700 (PDT)
Message-ID: <10103002.post@talk.nabble.com> (raw)
I have a table that contains a column for keywords that I expect to become
quite large and will be used for web searches. I will either index the
column or come up with a simple hashing algorithm add the hash key to the
table and index that column.
I am thinking the max length in the keyword column I need to support is 30,
but the average would be less than10
Any suggestions on whether to use char(30), varchar(30) or text, would be
appreciated. I am looking for the best performance option, not necessarily
the most economical on disk.
Or any other suggestions would be greatly appreciated.
--
View this message in context: http://www.nabble.com/seeking-advise-on-char-vs-text-or-varchar-in-search-table-tf3618204.html#a1010...
Sent from the PostgreSQL - performance mailing list archive at Nabble.com.
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: chrisj.wood@sympatico.ca
Subject: Re: seeking advise on char vs text or varchar in search table
In-Reply-To: <10103002.post@talk.nabble.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