forcing compression of text field

Поиск
Список
Период
Сортировка
Искать
От
Jonathan Ellis
Тема
forcing compression of text field
Дата
Msg-id
e06563880612110818s20d5f2a2sb9c469c2d87567e3@mail.gmail.com
Список
Дерево обсуждения
forcing compression of text field "Jonathan Ellis" <jonathan@utahpython.org>
Re: forcing compression of text field Jeff Davis <pgsql@j-davis.com>
Re: forcing compression of text field Scott Marlowe <smarlowe@g2switchworks.com>
Re: forcing compression of text field Tom Lane <tgl@sss.pgh.pa.us>
Re: forcing compression of text field Bruce Momjian <bruce@momjian.us>
Re: forcing compression of text field Ron Johnson <ron.l.johnson@cox.net>
I have a table of log messages.  They are mostly in the 100-200
character length, which apparently isn't large enough for PG to want
to compress it (length == octet_length).  I really need to save disk
space.  I can store it as a bytea and compress it manually (zlib level
1 compression gives about 50% savings), but is there a way to force
pg's own compression before I resort to this?

-- 
Jonathan Ellis
http://spyced.blogspot.com
В списке pgsql-general по дате отправления
От: Magnus Hagander
Дата:
Сообщение: Re: tsearch2 and pdf files
От: Bruce Momjian
Дата:
FAQ