From: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
---|---|
To: | Luca Pireddu <luca(at)cs(dot)ualberta(dot)ca> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: argument type problem with plpgsql function |
Date: | 2005-11-23 00:13:28 |
Message-ID: | 20051122161059.H87037@megazone.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On Tue, 22 Nov 2005, Luca Pireddu wrote:
> I wrote a little function that has to work with big numbers
>
> CREATE OR REPLACE FUNCTION blast_evalue(seq_len bigint, db_size bigint,
> bit_score double precision)
> RETURNS double precision AS $$
> BEGIN
> RETURN 2^(bit_score) * db_size * seq_len;
> END;
> $$
> LANGUAGE 'plpgsql'
> IMMUTABLE
> RETURNS NULL ON NULL INPUT;
>
> but it doesn't work properly unless I cast the db_size parameter when I call
> the function:
>
> select blast_evalue(273, 8903836, -55.4546);
> blast_evalue
> --------------
> 2430747228 <- wrong number. This is 273 * 8903836
> (1 row)
>
> select blast_evalue(273, 8903836::bigint, -55.4546);
> blast_evalue
> ---------------------
> 4.9231356421437e-08 <- that's correct
> (1 row)
>
> I don't understand why the cast is necessary. Is there a way to make this
> work without it?
I got the same answer (the second) for both calls from my 8.0 and 8.1
setups, what version were you trying on?
From | Date | Subject | |
---|---|---|---|
Next Message | Luca Pireddu | 2005-11-23 02:22:30 | Re: argument type problem with plpgsql function |
Previous Message | Luca Pireddu | 2005-11-23 00:08:09 | argument type problem with plpgsql function |