| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Richard Guo <guofenglinux(at)gmail(dot)com>, borz_off(at)cs(dot)msu(dot)su, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #17579: 15beta2: strange error when trying to use MERGE statement as a CTE |
| Date: | 2022-08-11 14:23:15 |
| Message-ID: | 485520.1660227795@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> On 2022-Aug-11, Tom Lane wrote:
>> The parse error location seems quite oddly chosen. Can you make
>> it point at the MERGE instead? I think exprLocation(cte->ctequery)
>> might work, but not sure.
> I tried, but couldn't find the location anywhere. None of the nodes for
> ModifyTable statements have location :-(
Ah, right, in particular MergeStmt doesn't.
> We could add one now -- while
> it's a bit late for 15, we're likely going to have a catversion bump due
> to the JSON revert, so it might be fine.
Nah, not worth it just for this.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ajin Cherian | 2022-08-11 15:04:30 | Re: Excessive number of replication slots for 12->14 logical replication |
| Previous Message | Alvaro Herrera | 2022-08-11 14:17:45 | Re: BUG #17579: 15beta2: strange error when trying to use MERGE statement as a CTE |