Hi, Fabien. The next CF will start so I want to restart the discussion.
> About "socket_timeout" > If you face the following situation, this parameter will be needed. If you feel that this situation can't happen or the use case is too limited, please point out so. > > I think that there is some kind of a misnomer: this is not a > > socket-level timeout, but a client-side query timeout, so it should be > named differently? > Yes, I think so. > > > I'm not sure how to name it, though. > Me too. Since I want to use the monitoring target as the parameter name, let's decide the parameter name while designing. > > I think that the way it works is a little extreme, basically the > > connection is aborted from within pqWait, and then restarted from scratch. Which motion seems to be uncomfortable? Or both? > > There is no clear way to know about the value of the setting (SHOW, > > \set, \pset...). That is a nice idea! If this parameter implementation is decide, I'll also add these features. > About "TCP_USER_TIMEOUT" > I introduce the test methods of TCP_USER_TIMEOUT. I only came up with this test methods with "iptables". Since this command can be used only by root, I didn't create a script. Best regards, --------------------- Ryohei Nagaura
