From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Philip Warner <pjw(at)rhyme(dot)com(dot)au>, Frank Joerdens <frank(at)joerdens(dot)de>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: How does TOAST compare to other databases' mechanisms? |
Date: | 2000-10-09 18:12:34 |
Message-ID: | 200010091812.OAA21855@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> Philip Warner <pjw(at)rhyme(dot)com(dot)au> 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(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2000-10-09 18:13:37 | Re: How does TOAST compare to other databases' mechanisms? |
Previous Message | Bruce Momjian | 2000-10-09 18:10:30 | Re: How does TOAST compare to other databases' mechanisms? |