LONG vs. Toaster - Mailing list pgsql-hackers

From wieck@debis.com (Jan Wieck)
Subject LONG vs. Toaster
Date
Msg-id m120CMQ-0003kLC@orion.SAPserv.Hamburg.dsh.de
Whole thread Raw
Responses Re: [HACKERS] LONG vs. Toaster
List pgsql-hackers
Well,

    AFAIK   we  had  a  consensus  on  making  "try  to  compress
    attributes  before  moving  off"  a   runtime,   per   column
    configuration option. And that's what I'm after.

    This  might  interfere with the LZTEXT data type as is. Since
    this new data type isn't released yet, I'll have to remove it
    again before freeze.  The compressor/decompressor will become
    part of the toaster.

    Needs to revert the changes to pg_rewrite too,  so  the  next
    release will NOT gain any bigger rules. But to release it and
    later fight problems that  I  already  see,  only  to  enable
    bigger rules right now, is IMHO the wrong decision.

    Any complaints?


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#========================================= wieck@debis.com (Jan Wieck) #

pgsql-hackers by date:

Previous
From: wieck@debis.com (Jan Wieck)
Date:
Subject: Tuple toaster (was: Re: LONG varsize - how to go on)
Next
From: wieck@debis.com (Jan Wieck)
Date:
Subject: T-O-A-S-T meaning