| From: | Michael Paesold <mpaesold(at)gmx(dot)at> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-patches(at)postgreSQL(dot)org, Gregory Stark <stark(at)enterprisedb(dot)com> |
| Subject: | Re: WIP: rewrite numeric division |
| Date: | 2007-06-19 17:37:40 |
| Message-ID: | 46781464.3080909@gmx.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Tom Lane wrote:
> I wrote:
...
> Now it's unlikely that real-world applications are going to be as
> dependent on the speed of div_var for long inputs as numeric_big is.
> And getting the right answer has to take priority over speed anyway.
> Still this is a bit annoying. Anyone see a way to speed it up, or
> have another approach?
>
> regards, tom lane
+1 for the change from me.
We use PostgreSQL for financial accounting stuff, including plpgsql
triggers and functions etc. And we use numeric for all that. I always
thought that numeric division was exact! :-) I never saw problem,
perhaps because we round to very few digits, but well.
Please apply this patch. I can accept the performance drop, as long as
there won't be bad surprises with correctness.
Best Regards
Michael Paesold
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2007-06-19 17:49:21 | more autovacuum fixes |
| Previous Message | Tom Lane | 2007-06-19 17:32:04 | Re: [HACKERS] 'Waiting on lock' |