Re: ldap: fix resource leak

From: Neil Conway <neilc(at)samurai(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org, pgsql-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: ldap: fix resource leak
Date: 2006-11-06 01:50:47
Message-ID: 1162777847.5692.362.camel@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On Sun, 2006-11-05 at 19:28 -0500, Tom Lane wrote:
> Come to think of it: either elog(ERROR) or a failure return from
> CheckLDAPAuth is going to lead directly to backend exit, so the
> whole thing is pretty much a cosmetic issue anyway.

Thanks for the feedback. Patch applied, with an additional fix (noticed
some minor infelicities in the usage of snprintf()).

-Neil

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Neil Conway 2006-11-06 03:25:24 Re: adminpack and pg_catalog
Previous Message Tom Lane 2006-11-06 00:28:48 Re: ldap: fix resource leak

Browse pgsql-patches by date

  From Date Subject
Next Message Brendan Jurd 2006-11-06 03:44:42 Indicate disabled triggers in \d
Previous Message Tom Lane 2006-11-06 00:28:48 Re: ldap: fix resource leak