From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | tih(at)Hamartun(dot)Priv(dot)NO (Tom I Helbekkmo) |
Cc: | meskes(at)topsystem(dot)de, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Bug? |
Date: | 1998-02-06 18:00:12 |
Message-ID: | 199802061800.NAA15035@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>
> Bruce Momjian said:
>
> > The only fix for this would be to read all integers in as 64-bit
> > integers, then do the conversion, but that could be a performance
> > problem.
>
> Michael Meskes answered:
>
> > I agree. And performance is important. I think explicit type
> > conversion is what we should do. Or is it asked for too much if the
> > user has to add a ::float8 to the number?
>
> Am I being dense here? Can there really be a significant performance
> hit in the parsing of a query? Let's say that it takes a millisecond
> extra to do the right thing with a number. Does it matter? How many
> queries per second can we expect to process anyway?
I don't know of standard ways to read in 64-bit integers.
--
Bruce Momjian
maillist(at)candle(dot)pha(dot)pa(dot)us
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1998-02-06 18:01:31 | Re: AW: AW: [HACKERS] Re: atttypmod of 0 |
Previous Message | Bruce Momjian | 1998-02-06 17:46:05 | Re: [HACKERS] Profile of current backend |