On Fri, Jan 2, 2009 at 10:44, Robert Haas <robertmh...@gmail.com> wrote: > Here, we have a case where the space savings are potentially much > larger, and the only argument against it is that someone might be > disappointed in the performance of substring operations, if they > happen to do any. What if they know that they don't want to do any > and want to get compression? Even if the benefit is only 1.5X on > their data rather than 10X, that seems like a pretty sane and useful > thing to want to do. It's easy to shut off compression if you don't > want it; if the system makes an arbitrary decision to disable it, how > do you get it back?
I think we could just add another toast storage type: alter table alter column set storage compress; ? It seems overkill to expose PGLZ_Strategy knobs per column... -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
