--- On Wed, 12/29/10, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> From: Robert Haas <robertmhaas(at)gmail(dot)com>
> Subject: Re: [DOCS] Words missing in the following txt
> To: "Leslie S Satenstein" <lsatenstein(at)yahoo(dot)com>
> Cc: pgsql-docs(at)postgresql(dot)org
> Date: Wednesday, December 29, 2010, 6:45 AM
> On Sun, Dec 26, 2010 at 8:28 PM,
> Leslie S Satenstein
> > In 8.1.1. Integer Types
> > The ending sentence in the 2nd paragraph reads...
> > The bigint type should only be used if the integer
> range is insufficient, because the latter is definitely
> > Integers are bigger or smaller, the sentence could
> read better if phrased as follows:
> > Use regular integers for fast efficient execution. The
> bigint type should only be used if the integer range is
> The original phrasing might be a little too cute in the
> sense that
> "the latter" could be taken to refer to "the integer range"
> than "the integer data type", but the intended meaning is
> obvious in context. I think your revised phrasing is
> more negative
> about bigints than we actually want to be. I think
> bigints also
> provide fast, efficient execution (compare with, say,
> numeric) but
> they are not AS fast as integers.
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
> Sent via pgsql-docs mailing list (pgsql-docs(at)postgresql(dot)org)
> To make changes to your subscription:
A good compromise is to perhaps consider the following.
The bigint type should only be used if the integer range is insufficient, because calculation with the latter is definitely faster.
In response to
pgsql-docs by date
|Next:||From: Leslie S Satenstein||Date: 2010-12-29 17:38:36|
|Subject: Re: Some comments about Julian Dates and possible bug. Please provide feedback.|
|Previous:||From: char101||Date: 2010-12-29 13:01:37|
|Subject: Re: missing manual|