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 1ovKsE-0007QK-5J for pgsql-general@arkaria.postgresql.org; Wed, 16 Nov 2022 16:02:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ovKsD-0006wY-0z for pgsql-general@arkaria.postgresql.org; Wed, 16 Nov 2022 16:02:49 +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 1ovKsC-0006vP-Mv for pgsql-general@lists.postgresql.org; Wed, 16 Nov 2022 16:02:48 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ovKsA-0004gn-D5 for pgsql-general@postgresql.org; Wed, 16 Nov 2022 16:02:47 +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 2AGG2iPk1348540; Wed, 16 Nov 2022 11:02:45 -0500 From: Tom Lane To: shashidhar Reddy cc: pgsql-general Subject: Re: unrecognized node type: 350 In-reply-to: References: <1339044.1668608877@sss.pgh.pa.us> Comments: In-reply-to shashidhar Reddy message dated "Wed, 16 Nov 2022 21:25:37 +0530" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1348538.1668614564.1@sss.pgh.pa.us> Date: Wed, 16 Nov 2022 11:02:44 -0500 Message-ID: <1348539.1668614564@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk shashidhar Reddy writes: > We have extensions like plpgsql_check and plprofiler. Hmm. My bet is that one of those needs an update. You could probably narrow things down by setting log_error_verbosity to "verbose" so that an error location shows in the postmaster log. regards, tom lane