Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 1FEEA9FA20A for ; Fri, 20 Apr 2007 11:24:17 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 11248-09 for ; Fri, 20 Apr 2007 11:23:54 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from talk.nabble.com (www.nabble.com [72.21.53.35]) by postgresql.org (Postfix) with ESMTP id 6CFF89FA10D for ; Fri, 20 Apr 2007 11:24:00 -0300 (ADT) Received: from [72.21.53.38] (helo=jubjub.nabble.com) by talk.nabble.com with esmtp (Exim 4.50) id 1Heu1m-0007b1-SV for pgsql-performance@postgresql.org; Fri, 20 Apr 2007 07:23:58 -0700 Message-ID: <10103002.post@talk.nabble.com> Date: Fri, 20 Apr 2007 07:23:58 -0700 (PDT) From: chrisj To: pgsql-performance@postgresql.org Subject: seeking advise on char vs text or varchar in search table MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: chrisj.wood@sympatico.ca X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/382 X-Sequence-Number: 24259 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#a10103002 Sent from the PostgreSQL - performance mailing list archive at Nabble.com.