Great thanks all. Can you give me any indication of the performance implications of setting pooling=false? -----Original Message----- From: francisco.figueiredo.jr@xxxxxxxxx [mailto:francisco.figueiredo.jr@xxxxxxxxx] On Behalf Of Francisco Figueiredo Jr. Sent: Tuesday, 19 August 2008 3:48 AM To: Magnus Hagander Cc: Kim Robinson; pgsql-general@xxxxxxxxxxxxxx Subject: Re: [GENERAL] Postres.exe Processes Hang On 8/18/08, Magnus Hagander Hi, all! As Magnus said, this is caused by the fact Npgsql does connection pool by default. You can change that by passing pooling=false in your connection string. You can get more info at manual.npgsql.org I hope it helps <magnus@xxxxxxxxxxxx> wrote: > Kim Robinson wrote: >> >> >> Hi, >> >> I am using the npgsql postgres data adaptor in a C# ASP.NET application. >> Each time the site establishes a new connection to the database a >> postgres.exe process is started. For some reason this process is not >> removed when the connection is closed. >> >> Any help would be greatly appreciated. > > Are you by any chance using some connection pooling that keeps it alive? > I don't remember what the default is in npgsql, but a lot of frameworks > have connection pooling enabled by default. > > //Magnus > > -- > Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general > -- Regards, Francisco Figueiredo Jr. http://fxjr.blogspot.com http://www.npgsql.org -- Regards, Francisco Figueiredo Jr. http://fxjr.blogspot.com http://www.npgsql.org
