| From: | Erik Rijkers <er(at)xs4all(dot)nl> |
|---|---|
| To: | Amit Langote <amitlangote09(at)gmail(dot)com>, vignesh C <vignesh21(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, e(dot)indrupskaya(at)postgrespro(dot)ru |
| Subject: | Re: SQL/JSON revisited |
| Date: | 2023-02-20 14:41:36 |
| Message-ID: | 86f0426a-e5c0-ab64-f4fe-bf8bd39bb176@xs4all.nl |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Op 20-02-2023 om 08:35 schreef Amit Langote:
>>
>
> Rebased again over queryjumble overhaul.
>
Hi,
But the following statement is a problem. It does not crash but it goes
off, half-freezing the machine, and only comes back after fanatic
Ctrl-C'ing.
select json_query(jsonb '[3,4]', '$[*]' returning bigint[] empty object
on error);
Can you have a look?
Thanks,
Erik Rijkers
PS
Log doesn't really have anything interesting:
2023-02-20 14:57:06.073 CET 1336 LOG: server process (PID 1493) was
terminated by signal 9: Killed
2023-02-20 14:57:06.073 CET 1336 DETAIL: Failed process was running:
select json_query(jsonb '[3,4]', '$[*]' returning bigint[] empty object
on error);
2023-02-20 14:57:06.359 CET 1336 LOG: terminating any other active
server processes
2023-02-20 14:57:06.667 CET 1336 LOG: all server processes terminated;
reinitializing
2023-02-20 14:57:11.870 CET 1556 LOG: database system was interrupted;
last known up at 2023-02-20 14:44:43 CET
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2023-02-20 14:45:00 | Re: Add WAL read stats to pg_stat_wal |
| Previous Message | Stephen Frost | 2023-02-20 14:40:18 | Re: psql \watch 2nd argument: iteration count |