pg.ddx.io pgsql-general@postgresql.org mailing list archive
help / color / mirror / Atom feedUnrecognized Node Type Warning
5+ messages / 2 participants
[nested] [flat]
* Unrecognized Node Type Warning
@ 2023-05-18 17:28 Arora, Nick <NARORA@wsgr.com>
2023-05-18 18:20 ` Re: Unrecognized Node Type Warning Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 5+ messages in thread
From: Arora, Nick @ 2023-05-18 17:28 UTC (permalink / raw)
To: pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
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".
Would appreciate your help diagnosing the issue and identifying steps to resolve.
Queries that reproduce the issue:
SELECT ('{0}'::int2[])[0];
WARNING: unrecognized node type: 110
int2
------
(1 row)
SELECT ('0'::int2vector)[0];
WARNING: unrecognized node type: 110
int2vector
------------
0
(1 row)
SELECT (indkey::int2[])[0] FROM pg_index limit 1;
WARNING: unrecognized node type: 110
indkey
--------
1
(1 row)
SELECT scores[1], scores[2], scores[3], scores[4] FROM (select('{10,12,14,16}'::int[]) AS scores) AS round;
WARNING: unrecognized node type: 110
WARNING: unrecognized node type: 110
WARNING: unrecognized node type: 110
WARNING: unrecognized node type: 110
scores | scores | scores | scores
--------+--------+--------+--------
10 | 12 | 14 | 16
(1 row)
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.
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Unrecognized Node Type Warning
2023-05-18 17:28 Unrecognized Node Type Warning Arora, Nick <NARORA@wsgr.com>
@ 2023-05-18 18:20 ` Tom Lane <tgl@sss.pgh.pa.us>
2023-05-18 18:52 ` Re: Unrecognized Node Type Warning Arora, Nick <NARORA@wsgr.com>
0 siblings, 1 reply; 5+ messages in thread
From: Tom Lane @ 2023-05-18 18:20 UTC (permalink / raw)
To: Arora, Nick <NARORA@wsgr.com>; +Cc: pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
"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
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Unrecognized Node Type Warning
2023-05-18 17:28 Unrecognized Node Type Warning Arora, Nick <NARORA@wsgr.com>
2023-05-18 18:20 ` Re: Unrecognized Node Type Warning Tom Lane <tgl@sss.pgh.pa.us>
@ 2023-05-18 18:52 ` Arora, Nick <NARORA@wsgr.com>
2023-05-18 19:38 ` Re: Unrecognized Node Type Warning Arora, Nick <NARORA@wsgr.com>
0 siblings, 1 reply; 5+ messages in thread
From: Arora, Nick @ 2023-05-18 18:52 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
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.
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Unrecognized Node Type Warning
2023-05-18 17:28 Unrecognized Node Type Warning Arora, Nick <NARORA@wsgr.com>
2023-05-18 18:20 ` Re: Unrecognized Node Type Warning Tom Lane <tgl@sss.pgh.pa.us>
2023-05-18 18:52 ` Re: Unrecognized Node Type Warning Arora, Nick <NARORA@wsgr.com>
@ 2023-05-18 19:38 ` Arora, Nick <NARORA@wsgr.com>
2023-05-18 20:05 ` Re: Unrecognized Node Type Warning Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 5+ messages in thread
From: Arora, Nick @ 2023-05-18 19:38 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
To provide more complete information:
Here is the name and version of each extension we have installed:
azure (1.0)
btree_gin (1.3)
citext (1.6)
pgcrypto (1.3)
plpgsql (1.0)
uuid-ossp (1.1)
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.
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Unrecognized Node Type Warning
2023-05-18 17:28 Unrecognized Node Type Warning Arora, Nick <NARORA@wsgr.com>
2023-05-18 18:20 ` Re: Unrecognized Node Type Warning Tom Lane <tgl@sss.pgh.pa.us>
2023-05-18 18:52 ` Re: Unrecognized Node Type Warning Arora, Nick <NARORA@wsgr.com>
2023-05-18 19:38 ` Re: Unrecognized Node Type Warning Arora, Nick <NARORA@wsgr.com>
@ 2023-05-18 20:05 ` Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 5+ messages in thread
From: Tom Lane @ 2023-05-18 20:05 UTC (permalink / raw)
To: Arora, Nick <NARORA@wsgr.com>; +Cc: pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
"Arora, Nick" <NARORA@wsgr.com> writes:
> Here is the name and version of each extension we have installed:
> azure (1.0)
> btree_gin (1.3)
> citext (1.6)
> pgcrypto (1.3)
> plpgsql (1.0)
> uuid-ossp (1.1)
I'm quite certain that none of the last five are causing this,
so you need to take it up with whoever provides "azure".
regards, tom lane
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2023-05-18 20:05 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2023-05-18 17:28 Unrecognized Node Type Warning Arora, Nick <NARORA@wsgr.com>
2023-05-18 18:20 ` Tom Lane <tgl@sss.pgh.pa.us>
2023-05-18 18:52 ` Arora, Nick <NARORA@wsgr.com>
2023-05-18 19:38 ` Arora, Nick <NARORA@wsgr.com>
2023-05-18 20:05 ` Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox