Re: Idle connections - Too many clients connected already - Mailing list pgsql-odbc

From Philippe Lang
Subject Re: Idle connections - Too many clients connected already
Date
Msg-id 6C0CF58A187DA5479245E0830AF84F420AFA5A@poweredge.attiksystem.ch
Whole thread Raw
In response to Idle connections - Too many clients connected already  ("Philippe Lang" <philippe.lang@attiksystem.ch>)
List pgsql-odbc
Hello,

I have already activated this option in the registry. It is necessary in order to avoid a connection drop when the
clientis idle for some time. 

But my problem is different here. I would like a connection to be dropped on the server when the client has
disconnected...

Philippe

-----Message d'origine-----
De : Richard Huxton [mailto:dev@archonet.com]
Envoyé : jeudi, 22. janvier 2004 11:33
À : Philippe Lang; pgsql-odbc@postgresql.org
Objet : Re: [ODBC] Idle connections - Too many clients connected already

On Thursday 22 January 2004 06:57, Philippe Lang wrote:
> Hello,
>
> After using Postgresql for a while, through ODBC / MS Access, I'm not
> able to connect to the server anymore. The server reports "Too many
> clients connected already".
[snip]
> Is there a way to avoid that? I cannot certifiy that clients will
> always close their connexions in a clean way. So, is the server able
> to check if clients are still alive, and close their connection if
> it's not the case?

You can set a timeout for the ODBC on each client. I can't remember if this is in the odbc driver settings panel or
where.Worst case, it's a registry setting. That should do what you want. 

--
  Richard Huxton
  Archonet Ltd


pgsql-odbc by date:

Previous
From: Frank Joerdens
Date:
Subject: OpenOffice: SetPos with data_at_exec not yet supported
Next
From: "Hiroshi Inoue"
Date:
Subject: Re: OpenOffice: SetPos with data_at_exec not yet supported