From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Adam H(dot) Pendleton" <fmonkey(at)fmonkey(dot)net> |
Cc: | <Michiel_Lange(at)actuera(dot)nl>, <mark(at)nsa(dot)co(dot)il>, <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: Keep-alive? |
Date: | 2003-10-09 20:35:04 |
Message-ID: | 03AF4E498C591348A42FC93DEA9661B84C5AD8@mail.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
> -----Original Message-----
> From: Adam H. Pendleton [mailto:fmonkey(at)fmonkey(dot)net]
> Sent: 09 October 2003 13:31
> To: Dave Page
> Cc: Michiel_Lange(at)actuera(dot)nl; mark(at)nsa(dot)co(dot)il;
> pgadmin-support(at)postgresql(dot)org
> Subject: Re: [pgadmin-support] Keep-alive?
>
> Dave Page wrote:
>
> >2) Implement SQL level keep alives. This could a be simple SELECT
> >version() query that is executed automatically after n seconds of
> >inactivity.
> >
> >
> >
> This is what I had in mind, an application (i.e., layer 7)
> level keep-alive.
OK, just fiddling around here - attached is a patch that implements a
heartbeat on the master connection to each server. Currently it beats
every 5 seconds, though this would be made configurable/disable-able.
It doesn't actually do much other than throw an error message if it gets
an unexpected response.
Thoughts, comments?
Regards, Dave.
Attachment | Content-Type | Size |
---|---|---|
Heartbeat.patch | application/octet-stream | 9.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Troels Arvin | 2003-10-09 21:09:12 | Cannot compile |
Previous Message | Adam H. Pendleton | 2003-10-09 12:31:13 | Re: Keep-alive? |