From: Yusuf W. <unicef2k@yahoo.com>
To: pgsql-performance@postgresql.org
Subject: Re: Performance: BigInt vs Decimal(19,0)
Date: Sat, 27 Sep 2003 19:39:36 -0700 (PDT)
Message-ID: <20030928023936.66818.qmail@web40408.mail.yahoo.com> (raw)
In-Reply-To: <2125.1064708769@sss.pgh.pa.us>
Now, I've got to convince my project's software
architech, that a bigint would be better than a
decimal.
Does anyone know where I could get some documentation
on how the int and decimal are implemented so I could
prove to him that ints are better? Can people suggest
good points to make in order to prove it?
Thanks in advance.
--- Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "Yusuf W." <unicef2k@yahoo.com> writes:
> > For the application that I'm working on, we want
> to
> > use data types that are database independent.
> (most
> > databases has decimal, but not big int).
>
> Most databases have bigint, I think.
>
> > Anyhow, we are planning on using decimal(19,0) for
> our
> > primary keys instead of a big int, would there be
> a
> > performance difference in using a bigint over
> using decimals?
>
> You'll be taking a very large performance hit, for
> very little benefit
> that I can see. How hard could it be to change the
> column declarations
> if you ever move to a database without bigint?
> There's not normally
> much need for apps to be explicitly aware of the
> column type names.
>
> regards, tom lane
__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
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: unicef2k@yahoo.com
Subject: Re: Performance: BigInt vs Decimal(19,0)
In-Reply-To: <20030928023936.66818.qmail@web40408.mail.yahoo.com>
* 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