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 1rKzwG-005VhJ-6s for pgsql-hackers@arkaria.postgresql.org; Wed, 03 Jan 2024 12:01:36 +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 1rKzwE-0051de-SP for pgsql-hackers@arkaria.postgresql.org; Wed, 03 Jan 2024 12:01:34 +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 1rKzwD-0051dE-8E for pgsql-hackers@lists.postgresql.org; Wed, 03 Jan 2024 12:01:34 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rKzw9-00FJvq-1L for pgsql-hackers@lists.postgresql.org; Wed, 03 Jan 2024 12:01:32 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id B5A7C5C0215; Wed, 3 Jan 2024 07:01:26 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 03 Jan 2024 07:01:26 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eisentraut.org; h=cc:cc:content-transfer-encoding:content-type:content-type :date:date:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:subject:subject:to:to; s=fm1; t=1704283286; x=1704369686; bh=3Aok1Hh/qMyTQLSQU1V94reuDM5yRoVV OSKjCWxuG7I=; b=OZSFJU5a3Vt+nJ3ecJmzc6xhzd+U6Zf4wyOGdrwF7St8QJij XY+nv7Rfe19wcICh/uDSP7fSXHEC+dgFyBMBW/Eh1+8436/IPLRrnltl9Pgdkudk bIw7+VuYsn9i+1fw9fp9ejkAbQg76PHE2EwVwbxns9HrvVA2Prt0j41nsQpWA2fU 66qec4QDDAqAyxieXshuhVXpnE+4lp8eBlalgR0dN9X4bZqoNKa3uWZJr5r16Yn0 hLi/UJmI/JgIh+DjPq01NtZOxbUH0eYM7QQJU1+0xwJ33xF4pMJ+VUWZ7v+5d7L5 LuyVxtqjsW1BBHxPlAIoEheKpTFXuM4rgAXSuQ== 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 :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1704283286; x= 1704369686; bh=3Aok1Hh/qMyTQLSQU1V94reuDM5yRoVVOSKjCWxuG7I=; b=0 ejretlYVHdeOhZmGIYhfLOY42kkXfgjszFseVFjjVHSQxGFb1GajyM0Av7ZgEbd/ XqaTsv3+RQpYoplD9hXdk5sKg2zbUBm+C9HUbqyGEEV4SKnfXDn5wMQGf/+HjZY0 hLYmaAhrXom2fAox6mAFU5V7EOBC/B4bOH4RVaKC5yc1o5r7A9Umtqk0Kz0VIkwm tO2jDtNJ0eEN7Cr05d1rz8B1F17aliFMaW/CMt1hHFxm7sz2T85CsSZhnv9xcbXn tMFf30rWz84TEOn4x0bdFLMCUmADXMqAe+aBVAHdPakKDxRZLa9LSU9Kk+dzV/PL rEiScYWM/lMab4xPKjPoQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrvdeghedgfeehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtjeertddtvdejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrsegvihhsvghnthhrrghuthdrohhrgh eqnecuggftrfgrthhtvghrnhepgfejtdfhkeeftdeugfeileehteeljeeghfeuledthfeu tedvffdukeefjefhgeehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomhepphgvthgvrhesvghishgvnhhtrhgruhhtrdhorhhg X-ME-Proxy: Feedback-ID: ie0a040ee:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 3 Jan 2024 07:01:25 -0500 (EST) Message-ID: Date: Wed, 3 Jan 2024 13:01:23 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: More new SQL/JSON item methods Content-Language: en-US To: Jeevan Chalke , Andrew Dunstan Cc: PostgreSQL Hackers References: <6d4feb29-6ced-a7b0-2c15-42d3e8e201f7@eisentraut.org> From: Peter Eisentraut In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 07.12.23 14:24, Jeevan Chalke wrote: > We have the same issue with integer conversion and need a fix. > > Unfortunately, I was using int8in() for the conversion of numeric > values. We should be using numeric_int8() instead. However, there is no > opt_error version of the same. > > So, I have introduced a numeric_int8_opt_error() version just like we > have one for int4, i.e. numeric_int4_opt_error(), to suppress the error. > These changes are in the 0001 patch. (All other patch numbers are now > increased by 1) > > I have used this new function to fix this reported issue and used > numeric_int4_opt_error() for integer conversion. I have committed the 0001 and 0002 patches for now. The remaining patches look reasonable to me, but I haven't reviewed them in detail.