| From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | Andrew Piskorski <atp(at)piskorski(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Compression and on-disk sorting |
| Date: | 2006-05-17 15:01:33 |
| Message-ID: | 20060517150132.GK26212@pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
If we're going to consider table-level compression, ISTM the logical
first step is to provide greater control over TOASTing; namely
thresholds for when to compress and/or go to external storage that can
be set on a per-field or at least per-table basis.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2006-05-17 15:04:13 | Re: Compression and on-disk sorting |
| Previous Message | Jim C. Nasby | 2006-05-17 14:56:07 | Re: Compression and on-disk sorting |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-05-17 15:38:05 | Re: Compression and on-disk sorting |
| Previous Message | Jim C. Nasby | 2006-05-17 14:56:07 | Re: Compression and on-disk sorting |