On Mon, Aug 18, 2008 at 9:59 PM, Kim Robinson <[EMAIL PROTECTED]> wrote:
> Great thanks all.
> Can you give me any indication of the performance implications of
> setting pooling=false?
>
Yeap. All the time you would need to connect to postgresql you will
have the overhead of tcp connection establ
; pgsql-general@postgresql.org
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
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
<[EMAIL PROTECTED]> wrote:
> Kim Robinson w
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
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.
Thank
