Re: In PG12, query with float calculations is slower than PG11

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,emre(at)hasegeli(dot)com
Cc: nospam-pg-abuse(at)bloodgate(dot)com,Amit Langote <amitlangote09(at)gmail(dot)com>,Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>,keisuke kuroda <keisuke(dot)kuroda(dot)3862(at)gmail(dot)com>,PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: In PG12, query with float calculations is slower than PG11
Date: 2020-02-13 16:41:38
Message-ID: 8CB3B0A2-8039-4306-AB10-4BAFBFDB2779@anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On February 13, 2020 8:30:45 AM PST, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>Emre Hasegeli <emre(at)hasegeli(dot)com> writes:
>>>> Cool. Emre, any chance you could write a patch along those lines?
>
>> How about the one attached?
>
>I see some minor things I don't like here, eg float_*flow_error()
>need some documentation as to why they exist. But I'll review,
>fix those things up and then push.

Would be good to mark them noreturn too.

Wonder if it's useful to add the"cold" marker to pg. Not as part of this patch, but for functions like these.

Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2020-02-13 16:47:59 Re: Small docs bugfix: make it clear what can be used in UPDATE FROM and DELETE USING
Previous Message Tom Lane 2020-02-13 16:30:45 Re: In PG12, query with float calculations is slower than PG11