From: Jochen Erwied <jochen@pgsql-performance.erwied.eu>
To: Tory M Blue <tmblue@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: bigint integers up to 19 digits.
Date: Thu, 4 Feb 2010 20:01:19 +0100
Message-ID: <1163141205.20100204200119@erwied.eu> (raw)
In-Reply-To: <8a547c841002041051i53d47fe4pf3a96e22bec85200@mail.gmail.com>
References: <8a547c841002041015o57d533fdg7237c50dea7a9278@mail.gmail.com>
<4B6B153D.9030200@emolecules.com>
<8a547c841002041051i53d47fe4pf3a96e22bec85200@mail.gmail.com>
Thursday, February 4, 2010, 7:51:37 PM you wrote:
> it is an identifier and is always a number and is used in grouping and
> querying. I thought I would lose performance if it is text vs an
> integer/double field.
Maybe using 'numeric(19)' instead of bigint is an alternative. I actually
don't know how these numbers are stored internally (some kind of BCD, or as
base-100?), but IMHO they should be faster than strings, although not as
fast as 'native' types.
--
Jochen Erwied | home: jochen@erwied.eu +49-208-38800-18, FAX: -19
Sauerbruchstr. 17 | work: joe@mbs-software.de +49-2151-7294-24, FAX: -50
D-45470 Muelheim | mobile: jochen.erwied@vodafone.de +49-173-5404164
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-performance@postgresql.org
Cc: jochen@pgsql-performance.erwied.eu, tmblue@gmail.com
Subject: Re: bigint integers up to 19 digits.
In-Reply-To: <1163141205.20100204200119@erwied.eu>
* 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