| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Arora, Nick" <NARORA(at)wsgr(dot)com> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Unrecognized Node Type Warning |
| Date: | 2023-05-18 18:20:13 |
| Message-ID: | 3866700.1684434013@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Arora, Nick" <NARORA(at)wsgr(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-05-18 18:23:17 | Re: Would PostgreSQL 16 native transparent data encryption support database level encryption? |
| Previous Message | Thorsten Glaser | 2023-05-18 18:02:35 | Re: Would PostgreSQL 16 native transparent data encryption support database level encryption? |