At 00:21 9/10/00 -0400, Tom Lane wrote:
>> But I also have images, most of which will _probably_ not
>> exceed a few hundred K. At which point do I cross the line where TOAST
...
>
>Good question. The answer probably depends on operational experience
>that we don't have yet (in other words, please try it both ways and
>report back ;-)).
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)? Or is this anothet case where we need to test - ie. CPU Vs. IO
availability?
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/
