| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Himanshu Upadhyaya <upadhyaya(dot)himanshu(at)gmail(dot)com>, Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru>, pgsql-hackers(at)postgresql(dot)org, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Oleg Bartunov <obartunov(at)postgrespro(dot)ru>, Erik Rijkers <er(at)xs4all(dot)nl> |
| Subject: | Re: SQL/JSON: functions |
| Date: | 2022-03-23 20:56:39 |
| Message-ID: | 20220323205639.GV28503@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Mar 23, 2022 at 03:49:17PM -0400, Andrew Dunstan wrote:
>
> On 3/23/22 08:24, Justin Pryzby wrote:
> > At least 0002-SQL-JSON-constructors-v64.patch has an issue with nodes,
> > per COPY_PARSE_PLAN_TREES.
> >
> > +ERROR: unrecognized node type: 157
>
> I just tried to reproduce this and was unable to. Ubuntu 20.04, gcc 9.4.0.
>
> the build was done with CPPFLAGS=-DCOPY_PARSE_PLAN_TREES. To be on the
> safe side I took ccache out of the equation.
>
> Can you give me any more details?
Sorry, the issue was actually with
#define RAW_EXPRESSION_COVERAGE_TEST
make check is enough to see it:
@@ -6,181 +6,78 @@
(1 row)
SELECT JSON_OBJECT(RETURNING json);
- json_object
--------------
- {}
-(1 row)
-
+ERROR: unrecognized node type: 157
[...]
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2022-03-23 20:58:31 | Re: Removing more vacuumlazy.c special cases, relfrozenxid optimizations |
| Previous Message | Peter Eisentraut | 2022-03-23 20:53:21 | Re: [PATCH] add relation and block-level filtering to pg_waldump |