Re: [PATCH]Remove obsolete macro CHECKFLOATVAL in btree_gist

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: "tanghy(dot)fnst(at)fujitsu(dot)com" <tanghy(dot)fnst(at)fujitsu(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH]Remove obsolete macro CHECKFLOATVAL in btree_gist
Date: 2021-08-19 03:28:07
Message-ID: YR3Px/s0W8lQkme5@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Aug 18, 2021 at 10:04:04AM +0900, Michael Paquier wrote:
> Yes, that does not seem wise on performance grounds. The case of
> !zero_is_valid is never reached, so it seems like this code was just a
> copy-paste from the float code in the backend. Your patch looks right
> to me.

Applied.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2021-08-19 03:29:44 Re: PG14: Avoid checking output-buffer-length for every encoded byte during pg_hex_encode
Previous Message Andrew Dunstan 2021-08-19 03:25:50 Re: support for windows robocopy in archive_command and restore_command