| From: | Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> |
|---|---|
| To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Fix NO_OOM handling in MemoryContextAllocAligned |
| Date: | 2026-08-04 04:45:35 |
| Message-ID: | FB315383-8BEF-4478-8C7A-C6D78EE27707@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Aug 4, 2026, at 12:11, David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
>
> On Mon, 3 Aug 2026 at 20:50, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> wrote:
>> MemoryContextAllocAligned() calls MemoryContextAllocExtended() and passes “flags" with only MCXT_ALLOC_ZERO removed. When “flags" includes MCXT_ALLOC_NO_OOM, MemoryContextAllocExtended() may return NULL, but MemoryContextAllocAligned() doesn't handle the returned NULL, which may
>> lead to a crash.
>
> Thanks. Pushed.
>
> David
Thanks for pushing.
Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Smith | 2026-08-04 05:11:44 | Add more tab=completion rules for DROP PROPERTY GRAPH |
| Previous Message | David Rowley | 2026-08-04 04:11:33 | Re: Fix NO_OOM handling in MemoryContextAllocAligned |