| From: | Aleksander Alekseev <aleksander(at)tigerdata(dot)com> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | Dmitry Kovalenko <d(dot)kovalenko(at)postgrespro(dot)ru> |
| Subject: | Re: BUG #18983: Problems with Postgres "make check" under ASAN |
| Date: | 2025-07-14 13:41:22 |
| Message-ID: | CAJ7c6TPe2+8kAJXFLC+zcFDV2==-SWHqvxiv8H97i8+EgnWq5A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi Dmitry,
> This is a flat list of problems (memory leaks):
>
> [...]
Thanks for your attention to the code correctness and quality.
In this project we typically don't bother about "cosmetic" memory
leaks - e.g. when several extra bytes are allocated during the process
startup, or many bytes are allocated in the short-living process (they
are going to be freed anyway when the process terminates).
If I didn't miss anything, your report contains only such cosmetic
leaks. If you believe I missed something, please don't hesitate
submitting a fix for a particular memory leak to pgsql-hackers(at)(dot)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2025-07-14 19:00:02 | BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti |
| Previous Message | Dmitry Kovalenko | 2025-07-14 12:33:23 | Re: BUG #18983: Problems with Postgres "make check" under ASAN |