Skip site navigation (1) Skip section navigation (2)

Re: seeking advise on char vs text or varchar in search table

From: "Merlin Moncure" <mmoncure(at)gmail(dot)com>
To: chrisj <chrisj(dot)wood(at)sympatico(dot)ca>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: seeking advise on char vs text or varchar in search table
Date: 2007-04-23 05:16:23
Message-ID: b42b73150704222216l1e56c331tfc8c7daa59a22499@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
On 4/20/07, chrisj <chrisj(dot)wood(at)sympatico(dot)ca> wrote:
>
> 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.

Don't use char...it pads out the string to the length always.   It
also has no real advantage over varchar in any practical situation.
Think of varchar as text with a maximum length...its no faster or
slower but the database will throw out entries based on length (which
can be good or a bad thing)...in this case, text feels better.

Have you looked at tsearch2, gist, etc?

merlin

In response to

Responses

pgsql-performance by date

Next:From: Andreas TilleDate: 2007-04-23 05:39:02
Subject: Re: postgres: 100% CPU utilization
Previous:From: Tom LaneDate: 2007-04-23 04:36:01
Subject: Re: postgres: 100% CPU utilization

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group