| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | John Moore <postgres(at)tinyvital(dot)com>, Postgresql Admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Performance impact of record sizes |
| Date: | 2002-07-05 00:09:04 |
| Message-ID: | 6488.1025827744@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> And in talking to the questioner, I was wondering if we have this
> auto-out-of-line TOAST description anywhere in the docs. If not, we
> need to add that.
Yes; I am not sure that that ever got into the main docs :-(.
We were so tickled with the notion that you no longer needed to
think about oversized fields, that we forgot that it ought to be
documented anyhow.
Jan's old TOAST project page,
http://www.ca.postgresql.org/projects/devel-toast.html
has some stuff that could be recycled into the manual, and I think
we have done some good writeups in response to older questions in
the mailing lists.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-07-05 00:10:34 | Re: Performance impact of record sizes |
| Previous Message | Bruce Momjian | 2002-07-05 00:02:01 | Re: Performance impact of record sizes |