Message-ID: <4C80208B.4060908@agliodbs.com>
Date: Thu, 02 Sep 2010 15:09:15 -0700
From: Josh Berkus <josh@agliodbs.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US;
	rv:1.9.1b3pre) Gecko/20090223 Thunderbird/3.0b2
MIME-Version: 1.0
To: pgsql-docs@postgreSQL.org
Subject: Correction: datatypes are not "faster"
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

All,

This is currently in:
http://www.postgresql.org/docs/current/interactive/datatype-numeric.html#DATATYPE-INT


"The type integer is the common choice, as it offers the best balance
between range, storage size, and performance. The smallint type is
generally only used if disk space is at a premium. The bigint type
should only be used if the integer range is insufficient, because the
latter is definitely faster."

This paragraph leaves a *lot* to be desired from an accuracy perspective
and encourages useless byte-counting by amateur performance geeks.  Instead:

The integer type is the most common choice, as it covers a sufficient
range for most operations requiring a non-decimal numeric value.  If,
however, you think you will want to store numbers greater than 2.4
billion, then use bigint.  Note that bigint will require more storage
space and memory.  When you have several integer columns in the same
table with values less than 32,000, you can sometimes achieve
significant space savings by using smallint instead of integer.
Otherwise, using smallint usually results in no real space or memory
savings.


-- 
                                  -- Josh Berkus
                                     PostgreSQL Experts Inc.
                                     http://www.pgexperts.com