pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Heikki Linnakangas <heikki@enterprisedb.com>
To: Kari Lavikka <tuner@bdb.fi>
Cc: pgsql-performance@postgresql.org
Subject: Re: Performance problem with table containing a lot of text (blog)
Date: Wed, 29 Aug 2007 11:14:20 +0100
Message-ID: <46D546FC.9070308@enterprisedb.com> (raw)
In-Reply-To: <Pine.HPX.4.62.0708291217250.3324@purple.bdb.fi>
References: <Pine.HPX.4.62.0708282016250.3324@purple.bdb.fi>
	<46D52E61.8020706@enterprisedb.com>
	<Pine.HPX.4.62.0708291217250.3324@purple.bdb.fi>

Kari Lavikka wrote:
> On Wed, 29 Aug 2007, Heikki Linnakangas wrote:
> 
>> The idea of being able to set the toast threshold per column was
>> discussed during 8.3 development, but no patch was produced IIRC. We
>> might do that in the future. If you're willing to compile from source,
>> you can lower TOAST_TUPLE_THRESHOLD.
> 
> We are currently using Postgres 8.1 but have to upgrade to 8.2 shortly.
> New version fixes some vacuum problems.
> 
> I always compile postgres from source. Maybe I have to do some
> calculations because that setting affects all tables and databases. Most
> of our text/varchar columns are quite short but setting the threshold
> too low causes excessive seeks to toast tables... right?

Right. If you have trouble finding the right balance, you can also use
ALTER STORAGE PLAIN to force the other columns not to be toasted.

-- 
  Heikki Linnakangas
  EnterpriseDB   http://www.enterprisedb.com



view thread (6+ messages)

Message-ID: <46D546FC.9070308@enterprisedb.com>
Permalink:  ../46D546FC.9070308@enterprisedb.com/
Also on:    postgresql.org/message-id/46D546FC.9070308@enterprisedb.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: heikki@enterprisedb.com, tuner@bdb.fi
  Subject: Re: Performance problem with table containing a lot of text (blog)
  In-Reply-To: <46D546FC.9070308@enterprisedb.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox