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

From: Emre Hasegeli <emre(at)hasegeli(dot)com>
To: Amit Langote <amitlangote09(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, keisuke kuroda <keisuke(dot)kuroda(dot)3862(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(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-07 14:30:54
Message-ID: CAE2gYzx3nEb0MbBwV1GtbmOYZ1TPKcPLOkeeZ8ZxFb=WCvX8sg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Fwiw, also tried the patch that Kuroda-san had posted yesterday.

I run the same test case too:

clang version 7.0.0:

HEAD 2548.119 ms
with patch 2320.974 ms

clang version 8.0.0:

HEAD 2431.766 ms
with patch 2419.439 ms

clang version 9.0.0:

HEAD 2477.493 ms
with patch 2365.509 ms

gcc version 7.4.0:

HEAD 2451.261 ms
with patch 2343.393 ms

gcc version 8.3.0:

HEAD 2540.626 ms
with patch 2299.653 ms

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2020-02-07 14:31:08 Re: Is custom MemoryContext prohibited?
Previous Message Kasahara Tatsuhito 2020-02-07 14:25:46 Re: Tid scan increments value of pg_stat_all_tables.seq_scan. (but not seq_tup_read)