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 1sEbQX-002QwK-Dn for pgsql-bugs@arkaria.postgresql.org; Tue, 04 Jun 2024 21:10:42 +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 1sEbQX-002eAo-EH for pgsql-bugs@arkaria.postgresql.org; Tue, 04 Jun 2024 21:10:41 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sEbCs-002bA4-UQ for pgsql-bugs@lists.postgresql.org; Tue, 04 Jun 2024 20:56:35 +0000 Received: from st43p00im-zteg10063401.me.com ([17.58.63.175]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sEbCl-003TU4-Px for pgsql-bugs@postgresql.org; Tue, 04 Jun 2024 20:56:33 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=osss.net; s=sig1; t=1717534585; bh=hAjWgwU/Wzqaq9NBVYIK8EbUGlevr9lGw90DbJnRADA=; h=From:Content-Type:Mime-Version:Subject:Message-Id:Date:To; b=Oolj4vtnsSR3NpkNCjihpCciwqUKAJ7WTg6gkeJC0QKMHvaNKr0MHVACdjeGp0CgC 0pt8JVSNOpIUGCa13vBAW3PuTRMQvYIUApN/FJez1zCQIWhYRQJAIcTvF1jBzvZJI6 mnycx/8aynJQHy8rU8SzNso4Q+rukj9zmmuaPEVjwz/m6kdcVaIIsA1VKZTLKYZCCD Bn03B1UTnOV0uKfAwgUViUjzcs5+GhT3ILVoyYQap8BdVGDaeeUEK8WkWiVfkG+jzB ytg9zHzHGyklWtJIzP7s77Tdb1mF4M0zdLRzt2tJweVvdLlyo/r75GN0A77/1GWGo3 0XzWxOwJvTL0w== Received: from smtpclient.apple (st43p00im-dlb-asmtp-mailmevip.me.com [17.42.251.41]) by st43p00im-zteg10063401.me.com (Postfix) with ESMTPSA id 2FAC4A80B63 for ; Tue, 4 Jun 2024 20:56:22 +0000 (UTC) From: Casey & Gina Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\)) Subject: intarray bigint support Message-Id: <3D34B57F-6AE9-4AFE-86FF-33BB858D7848@osss.net> Date: Tue, 4 Jun 2024 15:56:20 -0500 To: "pgsql-bugs@postgresql.org" X-Mailer: Apple Mail (2.3774.600.62) X-Proofpoint-GUID: XhQFEHws2cyk5dCgrKm7wN2hx8CO8ZGy X-Proofpoint-ORIG-GUID: XhQFEHws2cyk5dCgrKm7wN2hx8CO8ZGy X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.272,Aquarius:18.0.1039,Hydra:6.0.680,FMLib:17.12.28.16 definitions=2024-06-04_09,2024-06-04_01,2024-05-17_01 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 spamscore=0 clxscore=1030 adultscore=0 mlxscore=0 bulkscore=0 mlxlogscore=450 phishscore=0 malwarescore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.19.0-2308100000 definitions=main-2406040143 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk I got excited about using intarray to replace a couple custom pl/pgsql = functions (namely for subtraction and sorting) that I'm currently = relying on, but then discovered that it doesn't support bigint arrays. = So it won't work for all of my use cases, since some IDs that are in the = arrays I'm working with are bigint. Thought I'd ask to see if it might = be a simple enough thing to add bigint support to the extension in a = future version? Thanks, --=20 Casey=