Re: TEXT field and Postgresql Perfomance

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruno Wolff III <bruno(at)wolff(dot)to>
Cc: "Loren M(dot) Lang" <lorenl(at)alzatex(dot)com>, PostgreSQL Perfomance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: TEXT field and Postgresql Perfomance
Date: 2005-01-08 05:49:07
Message-ID: 3333.1105163347@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Bruno Wolff III <bruno(at)wolff(dot)to> writes:
> 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.

You are overlooking the effects of TOAST. Fields wider than a kilobyte
or two will be pushed out-of-line and will thereby not impose a penalty
on queries that only access the other fields in the table.

(If Loren's notion of "large" is "a hundred bytes" then there may be a
measurable impact. If it's "a hundred K" then there won't be.)

regards, tom lane

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Jeffrey Tenny 2005-01-08 21:07:00 Null integer columns
Previous Message Michael Fuhr 2005-01-08 05:23:13 Re: TEXT field and Postgresql Perfomance