| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Amit Langote <amitlangote09(at)gmail(dot)com> |
| Cc: | Tender Wang <tndrwang(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, exclusion(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault |
| Date: | 2024-10-16 14:26:39 |
| Message-ID: | 71060.1729088799@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Amit Langote <amitlangote09(at)gmail(dot)com> writes:
> Also, it might be better to leave a comment where the commit is
> removing code, as follows:
> - if (WALK(jve->raw_expr))
> - return true;
> + /* Ignore raw_expr because it's not relevant at runtime. */
Would it be better for parse analysis to explicitly NULL out this
field once it's done looking at it? Carrying unmaintained pieces
of an expression tree around seems both inefficient and prone to
future failures of this same ilk. The further the raw_expr gets
out of step with current reality, the worse the hazards.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ba Jinsheng | 2024-10-16 14:56:54 | Re: Performance Issue on Query 18 of TPC-H Benchmark |
| Previous Message | Tender Wang | 2024-10-16 14:14:31 | Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault |