From: Tom Lane <tgl@sss.pgh.pa.us>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-docs@postgresql.org
Subject: Re: Correction: datatypes are not "faster"
Date: Thu, 02 Sep 2010 18:13:39 -0400
Message-ID: <15330.1283465619@sss.pgh.pa.us> (raw)
In-Reply-To: <4C80208B.4060908@agliodbs.com>
References: <4C80208B.4060908@agliodbs.com>
Josh Berkus <josh@agliodbs.com> writes:
> "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
Really? Exactly which statements will you claim are incorrect?
I notice that your proposed rewrite omits the bit about bigint being
slower, which I can only conclude means you haven't tested on any
32-bit platforms lately.
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-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, josh@agliodbs.com
Subject: Re: Correction: datatypes are not "faster"
In-Reply-To: <15330.1283465619@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