| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
| Cc: | Alexander Lakhin <exclusion(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18374: Printing memory contexts on OOM condition might lead to segmentation fault |
| Date: | 2024-03-06 21:21:23 |
| Message-ID: | 313082.1709760083@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Alexander Korotkov <aekorotkov(at)gmail(dot)com> writes:
> For removing recursion from memory context processing, please check
> the patch by Heikki [1], and my slightly revised version [2].
> Links.
> 1. https://www.postgresql.org/message-id/6b48c746-9704-46dc-b9be-01fe4137c824%40iki.fi
> 2. https://www.postgresql.org/message-id/CAPpHfdtQVzkKgrxqKZE9yESnu7cAATVQbGktVOSXPNWG7GOkhA%40mail.gmail.com
I'd forgotten about that thread. I'll comment there, thanks!
The issue Alexander has identified about the kernel possibly not
giving us as much stack as promised should stay in this thread,
but we can discuss the idea of de-recursing mcxt.c over there.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2024-03-06 22:40:57 | Re: BUG #18314: PARALLEL UNSAFE function does not prevent parallel index build |
| Previous Message | PG Bug reporting form | 2024-03-06 21:18:24 | BUG #18380: BUG: notify stops working after LEFT JOIN if enable_mergejoin is ON |