Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Effect of large text field data on queries
- From: Glen Parker <glenebob(at)nwlink(dot)com>
- To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Cc: Postgres General <pgsql-general(at)postgresql(dot)org>
- Subject: Re: Effect of large text field data on queries
- Date: Thu, 26 Oct 2006 13:32:26 -0700
Tom Lane wrote:
Glen Parker <glenebob(at)nwlink(dot)com> writes:Why would very large text values effect the speed of a seq scan that does not actually evaluate those values?I'd actually suppose it's the smaller values (up to a few hundred bytes) that impact this the most. Really wide fields would be pushed out-of-line.
Meaning that the portion of the text value stored in the companion TOAST table would be ignored for this type of query, correct? That's why I'm concerned.
How much of a TOAST'd field is actually stored in the main heap table? Is there a way to configure that amount?
-Glen
- Follow-Ups:
- Re: Effect of large text field data on queries
- From: Tom Lane
- Re: Effect of large text field data on queries
- References:
- Effect of large text field data on queries
- From: Glen Parker
- Re: Effect of large text field data on queries
- From: Tom Lane
- Effect of large text field data on queries
- Prev by Date: Re: Effect of large text field data on queries
- Next by Date: Re: Effect of large text field data on queries
- Previous by thread: Re: Effect of large text field data on queries
- Next by thread: Re: Effect of large text field data on queries
- Indexes: