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 1pziEe-0001wR-3O for pgsql-general@arkaria.postgresql.org; Thu, 18 May 2023 18:20:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pziEc-0008T4-KJ for pgsql-general@arkaria.postgresql.org; Thu, 18 May 2023 18:20:18 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pziEc-0008Sf-9l for pgsql-general@lists.postgresql.org; Thu, 18 May 2023 18:20:18 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pziEY-000Zu2-VD for pgsql-general@lists.postgresql.org; Thu, 18 May 2023 18:20:17 +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 34IIKDbX3866701; Thu, 18 May 2023 14:20:14 -0400 From: Tom Lane To: "Arora, Nick" cc: "pgsql-general@lists.postgresql.org" Subject: Re: Unrecognized Node Type Warning In-reply-to: References: Comments: In-reply-to "Arora, Nick" message dated "Thu, 18 May 2023 17:28:38 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3866699.1684434013.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Thu, 18 May 2023 14:20:13 -0400 Message-ID: <3866700.1684434013@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk "Arora, Nick" writes: > We are using PostgreSQL 12.13. We are noticing that queries that attempt= to retrieve an element of an array by specifying its position cause a war= ning to be emitted: "WARNING: unrecognized node type: 110". I don't see that here, so I'm guessing it's coming from some extension. What extensions do you have loaded? Node type 110 would be T_SubscriptingRef in v12, which is a type name that didn't exist in earlier versions (it used to be called ArrayRef), so it's not very hard to believe that some extension missed out support for that type. But the only core-PG suspect is pg_stat_statements, and I can see that it does know that node type. regards, tom lane