| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Theo Schlossnagle <jesus(at)omniti(dot)com> |
| Cc: | PostgreSQL-development Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: double and numeric conversion |
| Date: | 2010-03-01 21:35:49 |
| Message-ID: | 24694.1267479349@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Theo Schlossnagle <jesus(at)omniti(dot)com> writes:
> I'm writing some extension and I have a hot code path that has a lot of double (C type) data and needs to output NUMERIC tuple data. The current methods I can find in the code to convert sprintf the double to a buffer and then invoke the numeric_in function on them. I've profile my stuff and I'm spending (wasting) all my time in that conversion. Is there a more efficient method of converting a double into a postgres numeric value?
If you're worried about micro-optimization, why are you using NUMERIC at
all? It's no speed demon.
Although you might be able to shave some cycles with a dedicated code
path for this conversion, binary to decimal is fundamentally not cheap.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Boszormenyi Zoltan | 2010-03-01 21:40:40 | Re: function side effects |
| Previous Message | Tom Lane | 2010-03-01 21:29:56 | Re: function side effects |