| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Dave Held" <dave(dot)held(at)arraysg(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Feature freeze date for 8.1 |
| Date: | 2005-05-03 21:20:06 |
| Message-ID: | 12111.1115155206@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Dave Held" <dave(dot)held(at)arraysg(dot)com> writes:
> How about an optional second connection to send keepalive pings?
> It could be unencrypted and non-blocking. If authentication is
> needed on the ping port (which it doesn't seem like it would need
> to be), it could be very simple, like this:
> * client connects to main port
> * server authenticates client normally
> * server sends nonce token for keepalive authentication
> * client connects to keepalive port
> * client sends nonce token on keepalive port
> * server associates matching keepalive connection with main
> connection
> * if server does not receive matching token within a small
> timeout, no keepalive support enabled for this session
This seems to have nothing whatever to do with the stated problem?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Swan | 2005-05-03 21:33:09 | Re: Feature freeze date for 8.1 |
| Previous Message | Dave Held | 2005-05-03 21:10:01 | Re: Feature freeze date for 8.1 |