From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Dave Held" <dave(dot)held(at)arrayservicesgrp(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: MAIN vs. PLAIN |
Date: | 2005-03-05 04:33:42 |
Message-ID: | 13975.1109997222@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
"Dave Held" <dave(dot)held(at)arrayservicesgrp(dot)com> writes:
> I notice that by default, postgres sets numeric fields to
> storage MAIN. What exactly does that mean?
See http://developer.postgresql.org/docs/postgres/storage-toast.html
There isn't any amazingly strong reason why numeric defaults to MAIN
rather than EXTENDED, which is the default for every other toastable
datatype --- except that I thought it'd be a good idea to have at
least one type that did so, just to exercise that code path in the
tuple toaster. And numeric shouldn't ordinarily be large enough to
need out-of-line storage anyway. It's unlikely even to need
compression, really, but as long as it's a varlena type the overhead
to support toasting is nearly nil.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Zoephel | 2005-03-05 12:26:37 | performance problems |
Previous Message | Alex Turner | 2005-03-05 00:15:55 | Re: multi billion row tables: possible or insane? |