From: | Hannu Krosing <hannu(at)skype(dot)net> |
---|---|
To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
Cc: | Andrew Piskorski <atp(at)piskorski(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Compression and on-disk sorting |
Date: | 2006-05-17 19:55:19 |
Message-ID: | 1147895720.3889.1.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Ühel kenal päeval, K, 2006-05-17 kell 10:01, kirjutas Jim C. Nasby:
> 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.
also, we would get a lot of "compression", if we could get rid of index
on toast table, and use the ctid directly.
--
----------------
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia
Skype me: callto:hkrosing
Get Skype for free: http://www.skype.com
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2006-05-17 20:02:37 | Re: PL/pgSQL 'i = i + 1' Syntax |
Previous Message | Jim C. Nasby | 2006-05-17 19:54:00 | Re: Compression and on-disk sorting |
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2006-05-17 20:20:07 | Re: Compression and on-disk sorting |
Previous Message | Jim C. Nasby | 2006-05-17 19:54:00 | Re: Compression and on-disk sorting |