| From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
|---|---|
| To: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
| Cc: | pgsql-general(at)postgresql(dot)org, Yang Zhang <yanghatespam(at)gmail(dot)com> |
| Subject: | Re: Compression |
| Date: | 2011-04-15 13:33:37 |
| Message-ID: | 201104150633.37778.adrian.klaver@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thursday, April 14, 2011 9:37:10 pm Craig Ringer wrote:
> On 15/04/2011 8:07 AM, Adrian Klaver wrote:
> > "EXTENDED allows both compression and out-of-line storage. This is the
> > default for most TOAST-able data types. Compression will be attempted
> > first, then out-of-
> >
> > line storage if the row is still too big. "
>
> Good point. I was unclear; thanks for pointing it out.
>
> What I was trying to say is that there's no whole-row compression, ie
> compression of the whole tuple except for minimal headers. A value in a
> field may be compressed, but you can't (say) compress a 100-column row
> of integers in Pg, because the individual fields don't support compression.
Got it now, thanks.
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shawn Gennaria | 2011-04-15 14:10:00 | Re: Migrating Data Across Major Versions |
| Previous Message | Adrian Klaver | 2011-04-15 13:32:19 | Re: Migrating Data Across Major Versions |