| 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: | 3DEF25F4.D92A5CF6@tpf.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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.
regards,
Hiroshi Inoue
http://w2422.nsk.ne.jp/~inoue/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Terry Yapt | 2002-12-05 10:37:31 | Schemas and ODBC driver. |
| Previous Message | Raymond O'Donnell | 2002-12-05 09:52:57 | Re: Connections sitting idle... |