DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=slZQ6En518B97Pm+Ul7yjXWr1NYxfFpxfB7VAMTBJwvWWa1Zevjgl3B0xsXYHhk0n4Qrlv2h+MmpVeaexIvlugc6bRUBSNXiEn9GBPuvWeM+/KsZsLigYEBpgVAu89zuVqMu3sq8DSt7d2NCCDTr9yJnbUL5OyMwndxdKe5ZlQY=;
Message-ID: <15263.96309.qm@web110704.mail.gq1.yahoo.com>
Date: Wed, 29 Dec 2010 09:25:32 -0800 (PST)
From: Leslie S Satenstein <lsatenstein@yahoo.com>
Subject: Re: Words missing in the following txt
To: Robert Haas <robertmhaas@gmail.com>
Cc: pgsql-docs@postgresql.org
In-Reply-To: <AANLkTi=VXxP+WwCB7YCBJrU3GACw89+cmaFPYPnOFVOk@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

=0A =0A=0A--- On Wed, 12/29/10, Robert Haas <robertmhaas@gmail.com> wrote:=
=0A=0A> From: Robert Haas <robertmhaas@gmail.com>=0A> Subject: Re: [DOCS] W=
ords missing in the following txt=0A> To: "Leslie S Satenstein" <lsatenstei=
n@yahoo.com>=0A> Cc: pgsql-docs@postgresql.org=0A> Date: Wednesday, Decembe=
r 29, 2010, 6:45 AM=0A> On Sun, Dec 26, 2010 at 8:28 PM,=0A> Leslie S Saten=
stein=0A> <lsatenstein@yahoo.com>=0A> wrote:=0A> > In 8.1.1. Integer Types=
=0A> >=0A> > The ending sentence in the 2nd paragraph reads...=0A> >=0A> > =
The bigint type should only be used if the integer=0A> range is insufficien=
t, because the latter is definitely=0A> faster.=0A> >=0A> > Integers are bi=
gger or smaller, the sentence could=0A> read better if phrased as follows:=
=0A> >=0A> > Use regular integers for fast efficient execution. The=0A> big=
int type should only be used if the integer range is=0A> insufficient.=0A> =
=0A> The original phrasing might be a little too cute in the=0A> sense that=
=0A> "the latter" could be taken to refer to "the integer range"=0A> rather=
=0A> than "the integer data type", but the intended meaning is=0A> pretty=
=0A> obvious in context.=A0 I think your revised phrasing is=0A> more negat=
ive=0A> about bigints than we actually want to be.=A0 I think=0A> bigints a=
lso=0A> provide fast, efficient execution (compare with, say,=0A> numeric) =
but=0A> they are not AS fast as integers.=0A> =0A> -- =0A> Robert Haas=0A> =
EnterpriseDB: http://www.enterprisedb.com=0A> The Enterprise PostgreSQL Com=
pany=0A> =0A> -- =0A> Sent via pgsql-docs mailing list (pgsql-docs@postgres=
ql.org)=0A> To make changes to your subscription:=0A> http://www.postgresql=
.org/mailpref/pgsql-docs=0A=0AA good compromise is to perhaps consider the =
following.=0A=0AThe bigint type should only be used if the integer range is=
 insufficient, because calculation with the latter is definitely faster.=0A