Re: Text/Varchar performance... - Mailing list pgsql-performance

From Ahmad Fajar
Subject Re: Text/Varchar performance...
Date
Msg-id SVONE1yEXUIEAOeIiGX0000000c@ki-communication.com
Whole thread Raw
In response to Text/Varchar performance...  ("Cristian Prieto" <cristian@clickdiario.com>)
Responses Re: Text/Varchar performance...  ("Steinar H. Gunderson" <sgunderson@bigfoot.com>)
List pgsql-performance
Dear Cristian,

If you need to index the field, you must know that it limit the length up to
1000 bytes. So if you need to index the field you must limit the field type,
ex: varchar(250), than you can index the field and you can gain better
perfomance in searching base on the fields, because the search uses the
index you have been created.
If you do not need to index the field, you can use the text field. Because
text field can store data up to 4 Gbytes.

Regards,
ahmad fajar

-----Original Message-----
From: pgsql-performance-owner@postgresql.org
[mailto:pgsql-performance-owner@postgresql.org] On Behalf Of Cristian Prieto
Sent: Kamis, 06 Oktober 2005 1:22
To: pgsql-general@postgresql.org; pgsql-performance@postgresql.org
Subject: [PERFORM] Text/Varchar performance...

Hello, just a little question, It's preferable to use Text Fields or
varchar(255) fields in a table? Are there any performance differences in the
use of any of them?

Thanks a lot for your answer!


---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

               http://archives.postgresql.org


pgsql-performance by date:

Previous
From: "Andy"
Date:
Subject: Re: Server misconfiguration???
Next
From: Stef
Date:
Subject: Compression of text columns