Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q8ok9-0002RR-Qa for pgsql-hackers@arkaria.postgresql.org; Mon, 12 Jun 2023 21:06:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q8ok8-0008Fi-Oh for pgsql-hackers@arkaria.postgresql.org; Mon, 12 Jun 2023 21:06:28 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q8ok8-0008FY-F4 for pgsql-hackers@lists.postgresql.org; Mon, 12 Jun 2023 21:06:28 +0000 Received: from new1-smtp.messagingengine.com ([66.111.4.221]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1q8ok1-001quZ-BP for pgsql-hackers@lists.postgresql.org; Mon, 12 Jun 2023 21:06:26 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailnew.nyi.internal (Postfix) with ESMTP id 92E7158026B; Mon, 12 Jun 2023 17:06:20 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Mon, 12 Jun 2023 17:06:20 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1686603980; x= 1686611180; bh=G2e9dqxyVReF5nJ++lpzBcC/iUummYEp36YoDkE1JoU=; b=C OY+YwLd0QSb3Bq/ySnNejLmd01LzsQU7Vc3sDdTK4Y3y1fyoIRWNxyHfdHipeOgm MfG8A8ALk4U67nSAZ0XBf1TvJL3ZDpUAJidKbVihW9tWtN1mZkroPQp9jwQPa81c szlpSm6qcvWYhzvAW+WZaRhuKSBX9HAQWt00lB0hif2zbbE1Nqre2Gj359b2uZwj l6IlJfUrxgW27yC0v9SybKYOyTVSCpdoOzWtvNk6dLsPoHoE4XnetXVEQBYPmCyW vk/fbPtp3/Lz0/Djf6+0TrcEh4/3a85UyuKFoKuhfZrIeTVvdqBPctmYn0MS5ywI CBNm0B0gxJr9DgyP7IkpA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrgeduhedgudehiecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnth gvrhhprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpeefjeegheetuefhveev udelueeftdejteeiffetvdduhfdtieefgfeutedtveeggfenucevlhhushhtvghrufhiii gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghu thesvghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Feedback-ID: i131946ab:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 12 Jun 2023 17:06:19 -0400 (EDT) Message-ID: <3020223d-6cdc-8e15-56e6-bc8cfc6c2d81@enterprisedb.com> Date: Mon, 12 Jun 2023 23:06:18 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: Shouldn't construct_array_builtin and deconstruct_array_builtin agree on types? Content-Language: en-US To: Tomas Vondra , PostgreSQL Hackers References: 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 12.06.23 22:38, Tomas Vondra wrote: > I noticed that these two function, introduced in d746021de18b, disagree > on what types they support. > I ran into this for INT4OID. Sure, I can just lookup the stuff and use > the regualr deconstruct_array, but the asymmetry seems a bit strange. Is > that intentional? They only support the types that they were actually being used with. If you need another type, feel free to add it.