| From: | jian he <jian(dot)universality(at)gmail(dot)com> |
|---|---|
| To: | Anthonin Bonnefoy <anthonin(dot)bonnefoy(at)datadoghq(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Set query_id for query contained in utility statement |
| Date: | 2024-10-15 13:22:53 |
| Message-ID: | CACJufxEQoSsU_BN8mzHeKckP5PUOKRxvDG419-wc3w9a68BNaQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
hi.
explain(verbose) SELECT 1, 2, 3\; explain SELECT 1, 2, 3, 4;
will transformed to
explain(verbose) SELECT 1, 2, 3; explain SELECT 1, 2, 3, 4;
it seems to me your patch care about following position.
explain(verbose) SELECT 1, 2, 3; explain SELECT 1, 2, 3, 4;
^
but this patch [1] at another thread will get the top level statement
(passed the raw parse, no syntax error) beginning more effortless.
explain(verbose) SELECT 1, 2, 3; explain SELECT 1, 2, 3, 4;
^ ^
can you try to looking at [1]. it may help to resolve this patch problem.
[1] https://www.postgresql.org/message-id/2245576.1728418678%40sss.pgh.pa.us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2024-10-15 13:27:46 | Re: simplify regular expression locale global variables |
| Previous Message | Peter Eisentraut | 2024-10-15 13:16:40 | Re: FOREIGN TABLE and IDENTITY columns |