| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrey Zhidenkov <pensnarik(at)gmail(dot)com> |
| Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #19108: Stack overflow duting query parse |
| Date: | 2025-11-10 16:02:48 |
| Message-ID: | 1879801.1762790568@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Andrey Zhidenkov <pensnarik(at)gmail(dot)com> writes:
>> Can you create a self-contained SQL script to reproduce this, and post it
>> on this thread with reply-all, please?
> Unfortunately, I cannot reproduce the issue even on an existing 15.7
> node (one that hasn't upgraded) (don't know if it matters, but now it's a
> hot standby node) but there are core dumps and debug info packages
> installed so I can provide more data from core dump.
Could you at least provide a not-mangled-to-the-point-of-incorrectness
version of the query? The posted one fails with
ERROR: table name "tablename_v2" specified more than once
and there are other visible bugs in it. Some clarity about the column
data types would be helpful as well.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-11-10 16:04:00 | Re: BUG #19107: The hold cursor is unexpectedly released during rollback |
| Previous Message | PG Bug reporting form | 2025-11-10 15:22:11 | BUG #19109: catalog lookup with the wrong snapshot during logical decoding causes coredump |