| From: | Tom I Helbekkmo <tih(at)Hamartun(dot)Priv(dot)NO> |
|---|---|
| To: | Michael Meskes <meskes(at)topsystem(dot)de> |
| Cc: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL Hacker <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [HACKERS] Bug? |
| Date: | 1998-02-06 16:55:57 |
| Message-ID: | 980206175035.28441B@barsoom.Hamartun.Priv.NO |
| 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?
-tih
--
Popularity is the hallmark of mediocrity. --Niles Crane, "Frasier"
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 1998-02-06 17:09:38 | Re: [HACKERS] Profile of current backend |
| Previous Message | Bruce Momjian | 1998-02-06 16:47:42 | Re: AW: [HACKERS] Re: atttypmod of 0 |