Re: Keep-alive?
От | Dave Page |
---|---|
Тема | Re: Keep-alive? |
Дата | |
Msg-id | 03AF4E498C591348A42FC93DEA9661B84C5AD5@mail.vale-housing.co.uk обсуждение исходный текст |
Ответ на | Keep-alive? ("Mark Rappoport" <mark@nsa.co.il>) |
Ответы |
Re: Keep-alive?
|
Список | pgadmin-support |
> -----Original Message----- > From: Adam H.Pendleton [mailto:fmonkey@fmonkey.net] > Sent: 09 October 2003 03:25 > To: Michiel_Lange@actuera.nl > Cc: mark@nsa.co.il; pgadmin-support@postgresql.org > Subject: Re: [pgadmin-support] Keep-alive? > > > On Wednesday, Oct 8, 2003, at 07:27 US/Eastern, > Michiel_Lange@actuera.nl wrote: > > > I think that adding an option to PgAdmin "send keepalive packages > > every <##> seconds" would be a valuable addition... > > > > I think this would be a much more viable solution than > re-connecting to > the database. No network level solution is viable for us unless we want to maintain our own replacement for libpq, besides which, even if we did implement some kind of icmp heartbeat, there's no guarantee it would help because it would be completely independent from any TCP connections - a firewall might still decide to close what it thinks are idle connections inspite of icmp messages. Istm that there are 2 options: 1) Implement reconnects in pgConn.cpp. The major objection to this is that the server may not notice that the original connection is dead, and thus a number of dead connections may build up until the connection limit on the server is reached. I think this problem is actually a bit irrelevant - as things stand at the moment, if you connection drops, you manually reconnect as soon as you need to. How many of us ever go and look for dead connections on the server, and even if you did, and found some, what would you do about it short of restarting the server? 2) Implement SQL level keep alives. This could a be simple SELECT version() query that is executed automatically after n seconds of inactivity. Thoughts? Regards, Dave.
В списке pgadmin-support по дате отправления: