| From: | John Naylor <johncnaylorls(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | memory context to complement ASAN |
| Date: | 2025-10-14 08:30:19 |
| Message-ID: | CANWCAZZ6MMfjBHMKVmvi_y_2zE9Y0H05rWtSBbxZcjR6dYQcDw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Some bugs have been found in ASAN builds using a compiled-in
malloc-only memory context (see commits 54ab74865, 1fe5a347e,
ccc8194e4 for the bugs fixed). The patch used was first mentioned here
(attachment: malloc_allocator.patch):
https://www.postgresql.org/message-id/193261e2c4d.3dd3cd7c1842.871636075166132237@zohocorp.com
Do we want something like this in core? I don't think we'd need the
ENABLE_ASAN symbol, since that seems orthogonal -- we can configure
ASAN separately how we wish, and I don't see why we'd need to tie the
GUC default for the special context to whether we use ASAN. Aside from
that, the basic idea seems useful.
--
John Naylor
Amazon Web Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dmitry Dolgov | 2025-10-14 08:35:55 | Re: Changing shared_buffers without restart |
| Previous Message | Chao Li | 2025-10-14 08:14:51 | Re: A tidyup of pathkeys.c |