Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gS6mP-00079M-BU for pgsql-bugs@arkaria.postgresql.org; Wed, 28 Nov 2018 20:49:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gS6mN-0006Ka-PE for pgsql-bugs@arkaria.postgresql.org; Wed, 28 Nov 2018 20:49:51 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gS6mN-0006It-HS for pgsql-bugs@lists.postgresql.org; Wed, 28 Nov 2018 20:49:51 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gS6mG-00083m-G9 for pgsql-bugs@lists.postgresql.org; Wed, 28 Nov 2018 20:49:51 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id wASKnebF014159; Wed, 28 Nov 2018 15:49:40 -0500 From: Tom Lane To: Victor Petrovykh cc: andrew@tao11.riddles.org.uk, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #15519: Casting float4 into int4 gets the wrong sign instead of "integer out of range" error In-reply-to: References: <15519-4fc785b483201ff1@postgresql.org> <874lc7sb1a.fsf@news-spur.riddles.org.uk> <13162.1543014227@sss.pgh.pa.us> <87zhtzqs9o.fsf@news-spur.riddles.org.uk> <15115.1543017152@sss.pgh.pa.us> <87va4nqr1a.fsf@news-spur.riddles.org.uk> <18151.1543023756@sss.pgh.pa.us> Comments: In-reply-to Victor Petrovykh message dated "Wed, 28 Nov 2018 13:14:17 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <14157.1543438180.1@sss.pgh.pa.us> Date: Wed, 28 Nov 2018 15:49:40 -0500 Message-ID: <14158.1543438180@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Victor Petrovykh writes: > I have one more related question: is a fix for this likely to appear in the > next Postgres release? Yes, it was pushed last week. https://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=e473e1f2b regards, tom lane