| From: | Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> |
|---|---|
| To: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Avoid use deprecated Windows Memory API |
| Date: | 2022-09-14 23:19:12 |
| Message-ID: | CAEudQAo3etqZWk5tht-2TCgo6JLGAFonn1pbaWY2ioaNXiBNNA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi.
According to:
https://docs.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-localalloc
"Note The local functions have greater overhead and provide fewer features
than other memory management functions. New applications should use the
heap functions unless documentation states that a local function should be
used. For more information, see Global and Local Functions."
LocalAlloc is deprecated.
So use HeapAlloc instead, once LocalAlloc is an overhead wrapper to
HeapAlloc.
Attached a patch.
regards,
Ranier Vilela
| Attachment | Content-Type | Size |
|---|---|---|
| use-heapalloc-instead-deprecated-localalloc.patch | application/octet-stream | 3.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2022-09-15 00:05:30 | Re: Counterintuitive behavior when toast_tuple_target < TOAST_TUPLE_THRESHOLD |
| Previous Message | Tom Lane | 2022-09-14 22:41:56 | Re: Use "WAL segment" instead of "log segment" consistently in user-facing messages |