pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Lewis Kapell <lkapell@setonhome.org>
Cc: pgsql-admin@postgresql.org
Subject: Re: TOAST behavior in 8.3 and 8.4
Date: Tue, 13 Apr 2010 15:22:26 -0400
Message-ID: <20100413192226.GE2990@alvh.no-ip.org> (raw)
In-Reply-To: <4BC4BBD4.40706@setonhome.org>
References: <4BC4BBD4.40706@setonhome.org>

Lewis Kapell wrote:
> I have a table with a text column, wherein most values range between
> 800 and 1700 bytes.  The data should be highly compressible, however
> these values appear to be too small to trigger the TOAST mechanism -
> I understand the default value of TOAST_TUPLE_THRESHOLD is about
> 2kb.


> However, I checked to see whether the behavior of TOAST had been
> changed in 8.4, since I am hoping to upgrade soon.  I found the
> following comment in the release notes:
> 
> "Consider TOAST compression on values as short as 32 bytes
> (previously 256 bytes)"

The 2kB are compared against tuple size.  The 32 bytes (previously 256)
are compared against a single column value.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support



view thread (5+ messages)  latest in thread

Message-ID: <20100413192226.GE2990@alvh.no-ip.org>
Permalink:  ../20100413192226.GE2990@alvh.no-ip.org/
Also on:    postgresql.org/message-id/20100413192226.GE2990@alvh.no-ip.org

 · 

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-admin@postgresql.org
  Cc: alvherre@commandprompt.com, lkapell@setonhome.org
  Subject: Re: TOAST behavior in 8.3 and 8.4
  In-Reply-To: <20100413192226.GE2990@alvh.no-ip.org>

* 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