Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sOIZs-00DXTc-21 for pgsql-hackers@arkaria.postgresql.org; Mon, 01 Jul 2024 15:04:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sOIZq-002mSi-Bt for pgsql-hackers@arkaria.postgresql.org; Mon, 01 Jul 2024 15:04:22 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sOIZp-002mRt-TU for pgsql-hackers@lists.postgresql.org; Mon, 01 Jul 2024 15:04:22 +0000 Received: from fout3-smtp.messagingengine.com ([103.168.172.146]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sOIZn-004VQZ-IW for pgsql-hackers@lists.postgresql.org; Mon, 01 Jul 2024 15:04:21 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.48]) by mailfout.nyi.internal (Postfix) with ESMTP id 341821380099; Mon, 1 Jul 2024 11:04:18 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Mon, 01 Jul 2024 11:04:18 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1719846258; x= 1719932658; bh=mYvy5NxEljfTjelxpVhVjLSfG5GeAMkdJygZ1TwsY10=; b=Q glkD2NFks5O3So/eqjeDht7ZXet5IsLxFe8i2yQajdl1stKHsPOVu7gA3KsJoqBW Xz5kJij0DubJirCAVhznKfWUP+MfxpNPkHwSGq/hFsmaJY7lhMTuKHX5/TX59+tT 2z/4oteSLQtqHznHN3hEg5kqPT+IO1hTN7N8vo5E7H54D99ujMoKJcy5rs8CfRNg h+0klw0Aje3A9hn1Mm2WV32g4aYLaTQ/uwKSPUbo+TjtGXvEIIolDuFTgWMmX3bA sYpSjuVhMzIHafAB8bO2uM1Z4LoCv7GlPziAdVmXDYJaWgySfhFD/qW9+QHAEh2p FUvZhXGnBtYHcCpNis8CQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeftddrudefgdekvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvvefukfggtggugfgjsehtkeertddttdejnecuhfhrohhmpeetlhhvrghr ohcujfgvrhhrvghrrgcuoegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhgqe enucggtffrrghtthgvrhhnpedvkedtffduffdtffffheffhfejjefhgfeiueeukeejkeff gfdufffhudffffeuveenucffohhmrghinhepvghnthgvrhhprhhishgvuggsrdgtohhmne cuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprghlvhhh vghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh X-ME-Proxy: Feedback-ID: ia2694551:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 1 Jul 2024 11:04:17 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alvh.no-ip.org; s=schmee; t=1719846256; bh=ycwteW75J9V4cdXcq8x56mDoPvMF6tm0ubYRxjBmzxc=; h=Date:From:To:Cc:Subject:In-Reply-To:From; b=TNzg27iZ3cN/G+wljlxikOyujhJhaF17sRw9Bp/X9aJbeKY6K5C7L+IEev/D1j2E1 XXgGWjcGdWRODpALQBeYaeam57Kq5sSDD5gFs24BMNajLA3xQM1DTQHb1bAtBf1APL CXm2c8UsGK3miO6Q0xueepbeqFPxVltqDeuiPL4WNzY3h1XEzh1ncVHSn2yH1hh190 fpgLvMUAfOuHjGunOI8+vrg5CUwTQ5uBNx/vf2GwyD8uuD7hSdpWM+z1qBQluOllrB 29cdybgbHwPRPCWhyvP8HEcmi0iRC/0Ra9/x57B7GfhqL7uGaizJasAyU8rCcjiVGL avFL74xm4a+mQ== Received: by schmee.alvh.no-ip.org (Postfix, from userid 1000) id 69D1D529; Mon, 1 Jul 2024 17:04:16 +0200 (CEST) Date: Mon, 1 Jul 2024 17:04:16 +0200 From: Alvaro Herrera To: Stepan Neretin Cc: Dean Rasheed , PostgreSQL Hackers Subject: Re: gamma() and lgamma() functions Message-ID: <202407011504.55hycgf74ix4@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2024-Jul-01, Stepan Neretin wrote: > I have one notice: > ERROR: value out of range: overflow. I think we need to add information > about the available ranges in the error message I think this is a project of its own. The error comes from calling float_overflow_error(), which is a generic routine used in several functions which have different overflow conditions. It's not clear to me that throwing errors listing the specific range for each case is worth the effort. -- Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/ "Escucha y olvidarás; ve y recordarás; haz y entenderás" (Confucio)