Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fIwjZ-0002Ad-DJ for pgsql-hackers@arkaria.postgresql.org; Wed, 16 May 2018 13:44:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fIwjY-00016w-3v for pgsql-hackers@arkaria.postgresql.org; Wed, 16 May 2018 13:44:48 +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_SHA384:256) (Exim 4.89) (envelope-from ) id 1fIwjX-00016m-T6 for pgsql-hackers@lists.postgresql.org; Wed, 16 May 2018 13:44:47 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fIwjU-0002vA-3e for pgsql-hackers@postgresql.org; Wed, 16 May 2018 13:44:47 +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 w4GDiWkW000497; Wed, 16 May 2018 09:44:32 -0400 From: Tom Lane To: Dean Rasheed cc: David Rowley , Bruce Momjian , =?UTF-8?B?xJDhurduZyBNaW5oIEjGsOG7m25n?= , PostgreSQL-development Subject: Re: NaNs in numeric_power (was Re: Postgres 11 release notes) In-reply-to: References: <20180511150852.GA18510@momjian.us> <20180514202850.GE5217@momjian.us> <18049.1526392887@sss.pgh.pa.us> <10898.1526421338@sss.pgh.pa.us> Comments: In-reply-to Dean Rasheed message dated "Wed, 16 May 2018 08:15:33 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <495.1526478272.1@sss.pgh.pa.us> Date: Wed, 16 May 2018 09:44:32 -0400 Message-ID: <496.1526478272@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Dean Rasheed writes: > On 15 May 2018 at 22:55, Tom Lane wrote: >> Here's a proposed patch for that. > In the case 1 ^ NaN = 1, what should the result scale be? The result is exact, so I don't see a reason to be worried about its scale. Messing with the scale would also require expending even more code on what is, in the end, a corner case that no users have expressed concern about. regards, tom lane