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 1tsot1-005qJ6-2c for pgsql-bugs@arkaria.postgresql.org; Thu, 13 Mar 2025 20:10:35 +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 1tsosz-004fxn-ME for pgsql-bugs@arkaria.postgresql.org; Thu, 13 Mar 2025 20:10:33 +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 1tsosz-004fxc-Dc for pgsql-bugs@lists.postgresql.org; Thu, 13 Mar 2025 20:10:33 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tsosv-002hwS-39 for pgsql-bugs@lists.postgresql.org; Thu, 13 Mar 2025 20:10:33 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 52DKAP6a2926484; Thu, 13 Mar 2025 16:10:25 -0400 From: Tom Lane To: ylshiyu@126.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #18840: Segmentation fault in executing select unnest(array(oidvector)) In-reply-to: <2557612.1741822653@sss.pgh.pa.us> References: <18840-fbc9505f066e50d6@postgresql.org> <2557612.1741822653@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Wed, 12 Mar 2025 19:37:33 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2926482.1741896625.1@sss.pgh.pa.us> Date: Thu, 13 Mar 2025 16:10:25 -0400 Message-ID: <2926483.1741896625@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk I wrote: > The crash you found is sufficient reason to back-patch 0001, even > though it changes results in some non-crash cases. I'm less sure > about whether to back-patch 0002. If anyone can find a crash > case involving ARRAY[], I think we should do so. After sleeping on it I concluded that both changes should be back-patched: if anyone were depending on ARRAY[] over int2vector or oidvector, you'd think they'd have noticed and reported the broken cases by now. Hence, pushed as one patch. regards, tom lane