pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedWords missing in the following txt
5+ messages / 3 participants
[nested] [flat]
* Words missing in the following txt
@ 2010-12-27 01:28 Leslie S Satenstein <lsatenstein@yahoo.com>
2010-12-29 11:45 ` Re: Words missing in the following txt Robert Haas <robertmhaas@gmail.com>
0 siblings, 1 reply; 5+ messages in thread
From: Leslie S Satenstein @ 2010-12-27 01:28 UTC (permalink / raw)
To: pgsql-docs
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 faster.
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 insufficient.
------------------
Regards
Leslie
Mr. Leslie Satenstein
mailto:lsatenstein@yahoo.com
mailto leslie.satenstein@itbms.biz / leslies@itbms.biz
www.itbms.biz
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Words missing in the following txt
2010-12-27 01:28 Words missing in the following txt Leslie S Satenstein <lsatenstein@yahoo.com>
@ 2010-12-29 11:45 ` Robert Haas <robertmhaas@gmail.com>
2010-12-29 17:25 ` Re: Words missing in the following txt Leslie S Satenstein <lsatenstein@yahoo.com>
0 siblings, 1 reply; 5+ messages in thread
From: Robert Haas @ 2010-12-29 11:45 UTC (permalink / raw)
To: Leslie S Satenstein <lsatenstein@yahoo.com>; +Cc: pgsql-docs
On Sun, Dec 26, 2010 at 8:28 PM, Leslie S Satenstein
<lsatenstein@yahoo.com> wrote:
> 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 faster.
>
> 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 insufficient.
The original phrasing might be a little too cute in the sense that
"the latter" could be taken to refer to "the integer range" rather
than "the integer data type", but the intended meaning is pretty
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
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Words missing in the following txt
2010-12-27 01:28 Words missing in the following txt Leslie S Satenstein <lsatenstein@yahoo.com>
2010-12-29 11:45 ` Re: Words missing in the following txt Robert Haas <robertmhaas@gmail.com>
@ 2010-12-29 17:25 ` Leslie S Satenstein <lsatenstein@yahoo.com>
2010-12-29 17:46 ` Re: Words missing in the following txt Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 5+ messages in thread
From: Leslie S Satenstein @ 2010-12-29 17:25 UTC (permalink / raw)
To: Robert Haas <robertmhaas@gmail.com>; +Cc: pgsql-docs
--- On Wed, 12/29/10, Robert Haas <robertmhaas@gmail.com> wrote:
> From: Robert Haas <robertmhaas@gmail.com>
> Subject: Re: [DOCS] Words missing in the following txt
> To: "Leslie S Satenstein" <lsatenstein@yahoo.com>
> Cc: pgsql-docs@postgresql.org
> Date: Wednesday, December 29, 2010, 6:45 AM
> On Sun, Dec 26, 2010 at 8:28 PM,
> Leslie S Satenstein
> <lsatenstein@yahoo.com>
> wrote:
> > 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
> faster.
> >
> > 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
> insufficient.
>
> The original phrasing might be a little too cute in the
> sense that
> "the latter" could be taken to refer to "the integer range"
> rather
> than "the integer data type", but the intended meaning is
> pretty
> 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@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-docs
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.
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Words missing in the following txt
2010-12-27 01:28 Words missing in the following txt Leslie S Satenstein <lsatenstein@yahoo.com>
2010-12-29 11:45 ` Re: Words missing in the following txt Robert Haas <robertmhaas@gmail.com>
2010-12-29 17:25 ` Re: Words missing in the following txt Leslie S Satenstein <lsatenstein@yahoo.com>
@ 2010-12-29 17:46 ` Tom Lane <tgl@sss.pgh.pa.us>
2010-12-30 04:18 ` Re: Words missing in the following txt Robert Haas <robertmhaas@gmail.com>
0 siblings, 1 reply; 5+ messages in thread
From: Tom Lane @ 2010-12-29 17:46 UTC (permalink / raw)
To: Leslie S Satenstein <lsatenstein@yahoo.com>; +Cc: Robert Haas <robertmhaas@gmail.com>; pgsql-docs
Leslie S Satenstein <lsatenstein@yahoo.com> writes:
> 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.
This doesn't seem to me to fix the basic problem, which is that "the
latter" appears to refer to "integer range". You don't calculate with
ranges, but with types. Maybe it should be
The bigint type should only be used if the range of the integer
type is insufficient, because the latter is definitely faster.
I'm not that excited about making the text specify that calculations are
faster, because on most modern machines the actual calculation speed
difference is pretty minuscule. What's expensive about bigint is
pushing around twice as much data and/or having to do palloc's.
regards, tom lane
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Words missing in the following txt
2010-12-27 01:28 Words missing in the following txt Leslie S Satenstein <lsatenstein@yahoo.com>
2010-12-29 11:45 ` Re: Words missing in the following txt Robert Haas <robertmhaas@gmail.com>
2010-12-29 17:25 ` Re: Words missing in the following txt Leslie S Satenstein <lsatenstein@yahoo.com>
2010-12-29 17:46 ` Re: Words missing in the following txt Tom Lane <tgl@sss.pgh.pa.us>
@ 2010-12-30 04:18 ` Robert Haas <robertmhaas@gmail.com>
0 siblings, 0 replies; 5+ messages in thread
From: Robert Haas @ 2010-12-30 04:18 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: Leslie S Satenstein <lsatenstein@yahoo.com>; pgsql-docs
On Wed, Dec 29, 2010 at 12:46 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Leslie S Satenstein <lsatenstein@yahoo.com> writes:
>> 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.
>
> This doesn't seem to me to fix the basic problem, which is that "the
> latter" appears to refer to "integer range". You don't calculate with
> ranges, but with types. Maybe it should be
>
> The bigint type should only be used if the range of the integer
> type is insufficient, because the latter is definitely faster.
>
> I'm not that excited about making the text specify that calculations are
> faster, because on most modern machines the actual calculation speed
> difference is pretty minuscule. What's expensive about bigint is
> pushing around twice as much data and/or having to do palloc's.
Yeah, I was actually wondering whether the first step here might be to
benchmark this.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2010-12-30 04:18 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2010-12-27 01:28 Words missing in the following txt Leslie S Satenstein <lsatenstein@yahoo.com>
2010-12-29 11:45 ` Robert Haas <robertmhaas@gmail.com>
2010-12-29 17:25 ` Leslie S Satenstein <lsatenstein@yahoo.com>
2010-12-29 17:46 ` Tom Lane <tgl@sss.pgh.pa.us>
2010-12-30 04:18 ` Robert Haas <robertmhaas@gmail.com>
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