X-Original-To: pgsql-sql-postgresql.org@postgresql.org
Received: from localhost (mx1.hub.org [200.46.208.251])
	by postgresql.org (Postfix) with ESMTP id 3DF3F9FB489
	for <pgsql-sql-postgresql.org@postgresql.org>;
	Fri, 25 Aug 2006 02:13:11 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024)
	with ESMTP id 68528-03 for <pgsql-sql-postgresql.org@postgresql.org>;
	Fri, 25 Aug 2006 02:13:02 -0300 (ADT)
X-Greylist: delayed 12:36:06.944731 by SQLgrey-
Received: from smtp20.kymp.net (smtp20.kymp.net [80.248.96.137])
	by postgresql.org (Postfix) with ESMTP id AAC8C9FB480
	for <pgsql-sql@postgresql.org>; Fri, 25 Aug 2006 02:13:01 -0300 (ADT)
Received: from [192.168.0.100] (static-241-66.kymp.net [213.130.241.66])
	by smtp20.kymp.net (8.13.3/8.13.3) with SMTP id k7P5CwOZ028754
	for <pgsql-sql@postgresql.org>; Fri, 25 Aug 2006 08:12:59 +0300
From: Aarni =?iso-8859-1?q?Ruuhim=E4ki?= <aarni@kymi.com>
Reply-To: aarni@kymi.com
Organization: KYMI.com
To: pgsql-sql@postgresql.org
Subject: Re: double precision vs. numeric
Date: Fri, 25 Aug 2006 08:12:58 +0300
User-Agent: KMail/1.6.2
References: <200608241936.50752.aarni@kymi.com>
 <7131.1156440586@sss.pgh.pa.us>
In-Reply-To: <7131.1156440586@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Message-Id: <200608250812.58794.aarni@kymi.com>
X-Virus-Scanned: by amavisd-new
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0.1 tagged_above=0 required=5 tests=AWL
X-Spam-Level: 
X-Archive-Number: 200608/198
X-Sequence-Number: 26156

On Thursday 24 August 2006 20:29, Tom Lane wrote:
> Aarni =3D?iso-8859-1?q?Ruuhim=3DE4ki?=3D <aarni@kymi.com> writes:
> > I vaguely remember having seen a message
> > ' ... type double precision ... will be depreciated / unsupported in
> > future releases ... '
> > or something like that somewhere. (?)
>
> Perhaps you are thinking of type "money"?  DOUBLE PRECISION is in the
> SQL standard, it's certainly not going anywhere.
>
>    regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>        choose an index scan if your joining column's datatypes do not
>        match

Well, I have used it for 'money type' like sums and prices but I have never=
=20
used the actual "money" data type.

So, false alarm.=20

Thank you guys !

Aarni
=2D-=20
Aarni Ruuhim=E4ki

**Kmail**
**Fedora Core Linux**