From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dave Held <dave.held@arrayservicesgrp.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: MAIN vs. PLAIN
Date: Fri, 04 Mar 2005 23:33:42 -0500
Message-ID: <13975.1109997222@sss.pgh.pa.us> (raw)
In-Reply-To: <49E94D0CFCD4DB43AFBA928DDD20C8F902618465@asg002.asg.local>
References: <49E94D0CFCD4DB43AFBA928DDD20C8F902618465@asg002.asg.local>
"Dave Held" <dave.held@arrayservicesgrp.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, dave.held@arrayservicesgrp.com
Subject: Re: MAIN vs. PLAIN
In-Reply-To: <13975.1109997222@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox