Tom Lane <tgl@sss.pgh.pa.us> writes:
> "Dave Held" <dave.held@arraysg.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
