| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Memory leak in vacuumlo |
| Date: | 2015-01-14 20:18:39 |
| Message-ID: | CA+TgmoYr-uyXUuw7HjmtqfVZxN8Xuy=XT_srXSbwqTK8aW2GBA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jan 13, 2015 at 2:58 AM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> Coverity has pointed out that vacuumlo.c is leaking memory when
> grabbing the list of candidate table names and schemas. Attached is a
> patch to fix the leak.
It's only leaking in error cases, the first of which is quite
unlikely. But I don't see that as a reason not to fix it, so --
committed.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2015-01-14 20:24:08 | Re: hung backends stuck in spinlock heavy endless loop |
| Previous Message | Tomas Vondra | 2015-01-14 20:02:59 | Re: PATCH: hashjoin - gracefully increasing NTUP_PER_BUCKET instead of batching |