| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | jora(dot)gevorgyan(at)rau(dot)am, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18338: Memory leak in function 'dumpRule' |
| Date: | 2024-02-12 14:04:28 |
| Message-ID: | E4B97C94-5E2C-4821-A8FA-0A922747F841@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> On 12 Feb 2024, at 14:36, PG Bug reporting form <noreply(at)postgresql(dot)org> wrote:
> The memory leak is found by a static analyzer developed at [CAST](
> https://www.linkedin.com/company/cast-center/).
Seems like they have some more work to do on their product.
> The memory alocated at [in qtabname]() is getting lost when function
> [pg_fatal is
> called](https://github.com/postgres/postgres/blob/09eb633e1baa3b7cd7929f3cc77f9c46f63c20b1/src/bin/pg_dump/pg_dump.c#L18007)
See src/include/common/logging.h: pg_fatal() calls exit(1), so there is no leak
here.
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2024-02-12 14:09:38 | Re: BUG #18338: Memory leak in function 'dumpRule' |
| Previous Message | PG Bug reporting form | 2024-02-12 13:36:13 | BUG #18338: Memory leak in function 'dumpRule' |