Tom Lane <tgl@sss.pgh.pa.us> writes:
> "Leonardo Francalanci" <lfrancalanci@simtel.ie> writes:
> > Could you point me to some docs on this TOAST-mechanism?
> > For instance: what kind of method is used to compress data?
>
> When in doubt, read the code ;-)
> src/backend/utils/adt/pg_lzcompress.c
> src/include/utils/pg_lzcompress.h
Are toasted values stored in the table itself or in a separate table?
My understanding was that it was the latter, which leads me to wonder whether
he'll actually gain anything by having all the records in his table be
toasted. It'll mean every record lookup has to traverse two indexes, and a
sequential scan loses the sequential read performance boost.
Or am I wrong and toasted values can be stored inline?
--
greg