On Tue, Jun 10, 2008 at 5:25 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Dawid Kuroczko" <[EMAIL PROTECTED]> writes:
>> As we already have four types of ALTER COLUMN .. SET STORAGE
>> { PLAIN | EXTERNAL | EXTENDED | MAIN } I would like to add
>> "COMPRESSED" which would force column compression (if
Dawid Kuroczko escribió:
> Currently the TOASTing code does its magic when whole tuple is
> larger than TOAST_TUPLE_TARGET which happens to be around 2KB.
>
> There are times though when one is willing to trade using (fast) CPU to
> reduce amount of (slow) I/O. A data warehousing types of worklo
"Dawid Kuroczko" <[EMAIL PROTECTED]> writes:
> As we already have four types of ALTER COLUMN .. SET STORAGE
> { PLAIN | EXTERNAL | EXTENDED | MAIN } I would like to add
> "COMPRESSED" which would force column compression (if column is
> smaller than some minimun, I guess somwehwere between 16 and 3
Dawid Kuroczko napsal(a):
Hello!
Currently the TOASTing code does its magic when whole tuple is
larger than TOAST_TUPLE_TARGET which happens to be around 2KB.
There are times though when one is willing to trade using (fast) CPU to
reduce amount of (slow) I/O. A data warehousing types of worklo
Hello!
Currently the TOASTing code does its magic when whole tuple is
larger than TOAST_TUPLE_TARGET which happens to be around 2KB.
There are times though when one is willing to trade using (fast) CPU to
reduce amount of (slow) I/O. A data warehousing types of workload
most notably. Rarely use
