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

Re: Connections sitting idle...

From: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
To: Raymond O'Donnell <rod(at)iol(dot)ie>
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: Connections sitting idle...
Date: 2002-12-05 10:09:56
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-odbc
Raymond O'Donnell wrote:
> On 5 Dec 2002 at 11:53, Hiroshi Inoue wrote:
> > Yes IIS uses the connection pooling mechanism by default.
> > Pooled connections would be re-used if possible for other
> > sessions without re-establishing new connections.
> I should have mentioned that I turned off connection pooling for the
> PostgreSQL ODBC driver to see would it make a difference, but the
> backends hung around anyway.

IIS can use connection pooling by itself.

> On the production system I will use
> pooling - if the backends are there, hopefully they'll be re-used
> rather than having new ones opened. I still have to try this out.
> > Anyway I can't see other sessions' info at all in your
> > example. How do other sessions behave ?
> The same thing happens consistently.

I saw no other session's log in your example between
'select * from surveyowners' and the call for PGAPI_
Disconnect. I'm wondering how the number of connections
increased in such a situation.

Hiroshi Inoue

In response to


pgsql-odbc by date

Next:From: Terry YaptDate: 2002-12-05 10:37:31
Subject: Schemas and ODBC driver.
Previous:From: Raymond O'DonnellDate: 2002-12-05 09:52:57
Subject: Re: Connections sitting idle...

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