Re: Higher TOAST compression.

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <jd(at)commandprompt(dot)com>
Cc: "Laurent Laborde" <kerdezixe(at)gmail(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Higher TOAST compression.
Date: 2009-07-17 19:21:09
Message-ID: 4A6088D50200002500028940@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Joshua D. Drake" <jd(at)commandprompt(dot)com> wrote:
> On Fri, 2009-07-17 at 12:50 -0500, Kevin Grittner wrote:

>> (3) Allow override of the thresholds for individual columns.

> I would skip 1 and 2 and have (3).

Sure, pick the one which requires new syntax! ;-)

How about two new ALTER TABLE actions:

ALTER [ COLUMN ] column SET COMPRESSION_THRESHOLD integer
ALTER [ COLUMN ] column SET EXTERNAL_THRESHOLD integer

Or can you suggest something better?

Laurent, would something like this address your needs? I was assuming
that if the point is to reduce I/O, you were interested in doing more
compression, not in storing more values out-of-line (in the separate
TOAST table)? Would it be manageable to tune this on a column-by-
column basis?

-Kevin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2009-07-17 19:36:39 Re: Higher TOAST compression.
Previous Message Heikki Linnakangas 2009-07-17 19:15:56 Re: more than one index in a single heap pass?