Tom Lane writes:
> There is something wrong with your system, not with Postgres. Any
> reasonable TCP stack will time out within circa 1 minute if no response.
>
> Example (sss is a machine on my LAN that's not presently up):
>
> $ time psql -h sss
> psql: PQconnectPoll() -- connect() failed: Co
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> I can observe something peculiar:
> [7.0.2 works different from current]
Interesting. The psql that I exhibited my test with was in fact 7.0.2
[quick check ... yes, current sources act the same]. So it does seem
there's something Linux-specific her
Grant <[EMAIL PROTECTED]> writes:
> Possibly create a timeout for psql. pg_dump, pg_restore and other clients.
> If they can not connect to a certain host within a certain period it will
> quit with an error. I have psql's still running for 6 days from crontab
> that could not connect to a bogus I
