Re: Higher TOAST compression.

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

Laurent Laborde <kerdezixe(at)gmail(dot)com> wrote:

> There is two compression strategy :
> static const PGLZ_Strategy strategy_default_data = {

> static const PGLZ_Strategy strategy_always_data = {

> 1) "strategy_always_data" seems to never be used.

A quick grep sure makes it look that way. I will look closer later.

> 2) the default strategy could be more aggressive (with a higher cpu
> cost)

> What about setting "PGLZ_strategy_always" as the default strategy
> (insane cpu cost ?) ?
> Or something in-between ?

That goes beyond what I was trying to do with my recent patch. What
you propose may be useful, but there would need to be much discussion
and benchmarking and it would be a new patch.

If you have any benchmark information on relative speed and space
savings, please post them.

-Kevin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Laurent Laborde 2009-07-20 16:15:07 Re: Higher TOAST compression.
Previous Message Joshua Brindle 2009-07-20 15:52:34 Re: [PATCH] SE-PgSQL/tiny rev.2193