Re: text vs varchar

From: Achilleus Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Wei Weng <wweng(at)kencast(dot)com>, <pgsql-sql(at)postgresql(dot)org>
Subject: Re: text vs varchar
Date: 2002-06-19 07:44:03
Message-ID: Pine.LNX.4.44.0206191042150.7003-100000@matrix.gatewaynet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

On Tue, 18 Jun 2002, Josh Berkus wrote:

> Wei,
>
> > Is there any disadvantage of using TEXT datatype as opposed to a VARCHAR
> > datatype with a maximum length, especially when I do searches on them?
>
> Yes. You can't index TEXT because it's of potentially unlimited length.

Well indexing text works fine for me.

Table "repdat"
Column | Type | Modifiers
-----------------+-----------------------------+-----------
vslid | integer |
vslname | character varying(15) |
orderno | integer | not null
date_in | timestamp without time zone |
port_landed | character varying(15) |
subject | text |
catid | integer |

dynacom=# EXPLAIN ANALYZE SELECT subject from repdat where subject='UTM
FOR SPECIAL SURVEY JUNE2000';
NOTICE: QUERY PLAN:

Index Scan using repdat_subject_idx on repdat (cost=0.00..7.40 rows=1
width=28) (actual time=0.05..0.06 rows=1 loops=1)
Total runtime: 0.10 msec

EXPLAIN
dynacom=#
dynacom=# SET enable_indexscan = off;
SET VARIABLE
dynacom=# EXPLAIN ANALYZE SELECT subject from repdat where subject='UTM
FOR SPECIAL SURVEY JUNE2000';
NOTICE: QUERY PLAN:

Seq Scan on repdat (cost=0.00..388.59 rows=1 width=28) (actual
time=0.03..8.14
rows=1 loops=1)
Total runtime: 8.19 msec

EXPLAIN
dynacom=#
>
>

--
Achilleus Mantzios
S/W Engineer
IT dept
Dynacom Tankers Mngmt
tel: +30-10-8981112
fax: +30-10-8981877
email: achill(at)matrix(dot)gatewaynet(dot)com
mantzios(at)softlab(dot)ece(dot)ntua(dot)gr

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Joachim Trinkwitz 2002-06-19 08:04:24 Aggregates not allowed in WHERE clause?
Previous Message Jerome Alet 2002-06-19 07:30:21 Help with a "recursive" query