Re: Feature freeze date for 8.1

From: Doug McNaught <doug(at)mcnaught(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Dave Held" <dave(dot)held(at)arraysg(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Feature freeze date for 8.1
Date: 2005-05-03 22:49:57
Message-ID: 87mzrb9b6y.fsf@asmodeus.mcnaught.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

> "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:
>
>
>
> This seems to have nothing whatever to do with the stated problem?

Yeah--one of the original scenarios was "firewall drops DB connection
because it's inactive." Pinging over a second socket does nothing to
address this.

If you want to make sure network connection X is up, testing network
connection Y, which happens to be between the same two processes, is
only helpful in a limited set of circumstances.

-Doug

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Chuck McDevitt 2005-05-03 22:54:41 Re: Feature freeze date for 8.1
Previous Message Dave Held 2005-05-03 22:40:30 Re: Feature freeze date for 8.1