npgsql - Npgsql2: [npgsql-open-discussion][1003946] RE: Connection leak

From: fxjr(at)pgfoundry(dot)org (User Fxjr)
To: pgsql-committers(at)postgresql(dot)org
Subject: npgsql - Npgsql2: [npgsql-open-discussion][1003946] RE: Connection leak
Date: 2008-09-01 20:58:26
Message-ID: 20080901205826.3476717AE731@pgfoundry.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------

[npgsql-open-discussion][1003946] RE: Connection leak in ExecuteReader/CloseConnection. Fixed a problem where Npgsql wasn't closing the connection if commandbehavior was said to close it and an error occured while executing ExecuteReader(CommandBehavior) method. Thanks Andrus Moor and Alaric Dailey for heads up and tests.

Modified Files:
--------------
Npgsql2/src/Npgsql:
NpgsqlCommand.cs (r1.26 -> r1.27)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/npgsql/Npgsql2/src/Npgsql/NpgsqlCommand.cs.diff?r1=1.26&r2=1.27)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2008-09-01 21:24:52 pgsql: Add a variant expected-output file for the sequence regression
Previous Message Tom Lane 2008-09-01 20:42:46 pgsql: Add a bunch of new error location reports to parse-analysis error