Re: Unrecognized Node Type Warning - Mailing list pgsql-general

From Arora, Nick
Subject Re: Unrecognized Node Type Warning
Date
Msg-id SN6PR03MB4542F569ED1D856B79B3E0FEA57F9@SN6PR03MB4542.namprd03.prod.outlook.com
Whole thread Raw
In response to Re: Unrecognized Node Type Warning  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Unrecognized Node Type Warning
List pgsql-general

Hello Tom,

Thanks for the information.  Here are the extensions we are using:

uuid-ossp

pgcrypto

citext

btree_gin

The warnings did start emitting shortly after the installation of btree_gin, so it seems somewhat suspect

 

 

From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Thursday, May 18, 2023 at 11:30 AM
To: Arora, Nick <NARORA@wsgr.com>
Cc: pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
Subject: Re: Unrecognized Node Type Warning

EXT - tgl@sss.pgh.pa.us

"Arora, Nick" <NARORA@wsgr.com> 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 warning 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



This email and any attachments thereto may contain private, confidential, and privileged material for the sole use of the intended recipient. Any review, copying, or distribution of this email (or any attachments thereto) by others is strictly prohibited. If you are not the intended recipient, please contact the sender immediately and permanently delete the original and any copies of this email and any attachments thereto.

pgsql-general by date:

Previous
From: Ron
Date:
Subject: Re: Would PostgreSQL 16 native transparent data encryption support database level encryption?
Next
From: Ron
Date:
Subject: Re: Would PostgreSQL 16 native transparent data encryption support database level encryption?