Hello,
> To wrap up, the relevant parameters work like this:
> * TCP keepalive and TCP user (retransmission) timeout: for network
problems
> * statement_timeout: for long-running queries
> * socket_timeout (or send/recv_timeout): for saturated servers
Takayuki Tsunakawa, could you provide wide
Hello Ryohei,
I took a look at your changes and I have some notes.
I faced the same issue as you faced. In my opinion hanging of a client is
quite critical case and it needs to be overcame.
TCP_USER_TIMEOUT option helps to overcome this problem and I agree with
you that it needs to be suppor
Hello ,
Did you take a look into the patches from the previous mail ?
What do you think about my proposal ?
Could you please say if there are any objections in regard to it?
Thank you in advance,
Andrei Yahorau
From: Andrei Yahorau/IBA
To: pgsql-hack...@postgresql.org,
Cc: Mikalai
Hello PostgreSQL Community!
Not long ago I faced the situation concerning ODBC/libpq client hanging in
case of some network problems.
I had a discussion regarding this issue within pgsql-o...@postgresql.org
and got some suggestions.
Here is this discussion:
https://www.postgresql.org/message-id
