| From: | "Francisco Figueiredo Jr(dot)" <francisco(at)npgsql(dot)org> |
|---|---|
| To: | "Magnus Hagander" <magnus(at)hagander(dot)net> |
| Cc: | "Kim Robinson" <Kim(dot)Robinson(at)hydro(dot)com(dot)au>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Postres.exe Processes Hang |
| Date: | 2008-08-18 17:47:30 |
| Message-ID: | 438d02260808181047v3106ccbaq81bf21d0d0ba8acc@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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(at)hagander(dot)net> 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(at)postgresql(dot)org)
> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mike Gould | 2008-08-18 18:25:38 | Fw: UUID vs Serial or BigSerial |
| Previous Message | Tom Lane | 2008-08-18 17:18:17 | Re: Re: pg_restore fails on Windows |