Re: TEXT field and Postgresql Perfomance

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: "Loren M(dot) Lang" <lorenl(at)alzatex(dot)com>
Cc: PostgreSQL Perfomance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: TEXT field and Postgresql Perfomance
Date: 2005-01-08 04:03:23
Message-ID: 20050108040323.GA13889@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Fri, Jan 07, 2005 at 19:36:47 -0800,
"Loren M. Lang" <lorenl(at)alzatex(dot)com> wrote:
> Do large TEXT or VARCHAR entries in postgresql cause any performance
> degradation when a query is being executed to search for data in a table
> where the TEXT/VARCHAR fields aren't being searched themselves?

Yes in that the data is more spread out because of the wider rows and that
results in more disk blocks being looked at to get the desired data.

> Since, according to the postgresql docs, theirs no performance
> difference between VARCHAR and TEXT, I'm assuming VARCHAR is identical
> to TEXT entries with a restriction set on the length. And since TEXT
> can be of any possible size, then they must be stored independently of

No.

> the rest of the table which is probably all stored in a fixed size rows

No, Postgres uses variable length records.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Alex Turner 2005-01-08 05:02:54 Re: TEXT field and Postgresql Perfomance
Previous Message Loren M. Lang 2005-01-08 03:36:47 TEXT field and Postgresql Perfomance