| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Ivan Kush <ivan(dot)kush(at)tantorlabs(dot)com>, pgsql-hackers mailing list <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [PATCH] Fix memory leak in pg_config |
| Date: | 2026-07-21 22:38:03 |
| Message-ID: | al_0y41Y7XnvrNYY@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jul 21, 2026 at 05:05:14PM -0400, Andres Freund wrote:
> So far our policy is that we do not care about leaks in short lived
> binaries. I doubt that we need more very verbose projects at this point, so I
> don't think we'll want to change this in the near future.
None of the changes proposed in the patch are worth caring about. The
only memory leaks I would care about in the frontend binaries are
those where we could run a tool in an infinite loop where the
non-freed would bloat. One example of that is pg_receivewal without
--no-loop, that could be used as a service to get WAL from a remote
source.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2026-07-21 22:49:34 | Re: [PATCH] Cover get_json_table_plan() with tests |
| Previous Message | Michael Paquier | 2026-07-21 22:35:01 | Re: [PATCH v1] Add vacuum_delay_point() to GiST empty-page deletion pass |