Re: How does TOAST compare to other databases' mechanisms?
От
Bruce Momjian
Тема
Re: How does TOAST compare to other databases' mechanisms?
Дата
Msg-id
200010091812.OAA21855@candle.pha.pa.us
Ответ на
Список
Дерево обсуждения
Re: How does TOAST compare to other databases' mechanisms? Frank Joerdens <frank@joerdens.de>
Re: How does TOAST compare to other databases' mechanisms? Tom Lane <tgl@sss.pgh.pa.us>
Re: How does TOAST compare to other databases'
mechanisms? Philip Warner <pjw@rhyme.com.au>
Re: How does TOAST compare to other databases' mechanisms? Tom Lane <tgl@sss.pgh.pa.us>
Re: How does TOAST compare to other databases' mechanisms? Bruce Momjian <pgman@candle.pha.pa.us>
Re: How does TOAST compare to other databases'
mechanisms? Philip Warner <pjw@rhyme.com.au>
Re: How does TOAST compare to other databases' mechanisms? Tom Lane <tgl@sss.pgh.pa.us>
Re: How does TOAST compare to other databases'
mechanisms? Philip Warner <pjw@rhyme.com.au>
Re: How does TOAST compare to other databases' mechanisms? Jan Wieck <janwieck@yahoo.com>
Re: How does TOAST compare to other databases' mechanisms? Tom Lane <tgl@sss.pgh.pa.us>
> Philip Warner writes: > > In the case of images, is there a way to tell TOAST not to bother even > > trying to compress the data? (eg. JPEG files). If so, would I be right in > > assuming that this would be better for fast retrieval (even for text > > files)? > > TOAST will not store a compressed value unless the compressed value is > smaller than the uncompressed by some reasonable amount (which looks to > be 20% by default). I'd expect JPEG-like data always to fail the Yea, I know, I have never heard of JPEG either, but Tom Lane is Mr. Internet JPEG, so humor him. :-) -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026
В списке pgsql-general по дате отправления
От: Bruce Momjian
Дата:
От: Bruce Momjian
Дата: