| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Robert Haas <rhaas(at)postgresql(dot)org>, pgsql-committers(at)postgresql(dot)org |
| Subject: | Re: pgsql: vacuumlo: Avoid unlikely memory leak. |
| Date: | 2015-07-21 13:29:08 |
| Message-ID: | 20150721132908.GE5596@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Michael Paquier wrote:
> On Thu, Jan 15, 2015 at 5:18 AM, Robert Haas <rhaas(at)postgresql(dot)org> wrote:
> > vacuumlo: Avoid unlikely memory leak.
> >
> > Spotted by Coverity. This isn't likely to matter in practice, but
> > there's no harm in fixing it.
>
> Coming back to this one, shouldn't this commit be backpatched?
I don't think it matters all that much, does it. It's unlikely and the
program is short-lived, so ...
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-07-21 13:29:32 | Re: pgsql: pg_upgrade: fix one-byte per empty db memory leak |
| Previous Message | Michael Paquier | 2015-07-21 13:01:55 | Re: pgsql: pg_upgrade: fix one-byte per empty db memory leak |