Horton

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

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: emre@hasegeli.com
Cc: Andres Freund <andres@anarazel.de>, nospam-pg-abuse@bloodgate.com, Amit Langote <amitlangote09@gmail.com>, Tomas Vondra <tomas.vondra@2ndquadrant.com>, keisuke kuroda <keisuke.kuroda.3862@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-02-13T16:30:45Z
Lists: pgsql-hackers 
Emre Hasegeli <emre@hasegeli.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.

			regards, tom lane

Commits

  1. Avoid a performance regression in float overflow/underflow detection.

  2. Provide separate header file for built-in float types