Skip site navigation (1) Skip section navigation (2)

Re: Higher TOAST compression.

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: "Laurent Laborde" <kerdezixe(at)gmail(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Higher TOAST compression.
Date: 2009-07-22 15:25:42
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Sorry I responded that quickly this early.  I keep having additional
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> wrote: 
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> And especially, how could you have per-column targets?
> Yeah, this would have to be done by table, not by column.
If we had an optional two targets by column, we could pass any columns
with such targets as a "step 0", before starting the tuple size
checks.  I think that makes sense, so I'm flip-flopping on that as a
Now, whether that's overkill is another question.

In response to

pgsql-hackers by date

Next:From: Andrew GierthDate: 2009-07-22 15:55:22
Subject: Re: revised hstore patch
Previous:From: Kevin GrittnerDate: 2009-07-22 15:08:11
Subject: Re: Higher TOAST compression.

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group