Skip site navigation (1) Skip section navigation (2)

Re: ldap: fix resource leak

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)postgresql(dot)org, Neil Conway <neilc(at)samurai(dot)com>
Cc: pgsql-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: ldap: fix resource leak
Date: 2006-11-05 04:34:52
Message-ID: 9974.1162701292@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Neil Conway <neilc(at)samurai(dot)com> writes:
> I fixed this by adding the appropriate ldap_unbind() calls in error
> control paths. An alternative would be to have a single place do the
> error handling, and jump to that via goto.

Perhaps use a PG_TRY construct?

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: markDate: 2006-11-05 06:15:51
Subject: PostgreSQL 8.2 (from CVS devel) first impressions
Previous:From: Neil ConwayDate: 2006-11-05 00:43:37
Subject: ldap: fix resource leak

pgsql-patches by date

Next:From: Simon RiggsDate: 2006-11-05 09:21:05
Subject: Re: Proposal: vacuum and autovacuum parameters to control freezing
Previous:From: Neil ConwayDate: 2006-11-05 00:43:37
Subject: ldap: fix resource leak

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group