RE: [patch]socket_timeout in interfaces/libpq

2019-11-28 Thread nagaura.ryo...@fujitsu.com
Hi, Michael-san. Sorry, I have missed your e-mail... > From: Michael Paquier > On Wed, Jun 26, 2019 at 11:56:28AM +, nagaura.ryo...@fujitsu.com wrote: > > It seems that you did not think so at that time. > > # Please refer to [1] > > > > I don't thi

RE: [patch]socket_timeout in interfaces/libpq

2019-06-27 Thread nagaura.ryo...@fujitsu.com
Hi, Michael-san. > From: Michael Paquier > On Wed, Jun 26, 2019 at 04:13:36AM +, nagaura.ryo...@fujitsu.com wrote: > > I don't think that the rest one of my proposals has been rejected > > completely, so I want to restart discussion. > I recall on the matter tha

[patch]socket_timeout in interfaces/libpq

2019-06-26 Thread nagaura.ryo...@fujitsu.com
Hello all. First, I'd like to appreciate with all your reviewing and discussion in the last CommitFest[1]. I don't think that the rest one of my proposals has been rejected completely, so I want to restart discussion. It is a timeout parameter in interfaces/libpq. Consider some situations whe

inheritance of connection paramters when using \c

2019-06-26 Thread nagaura.ryo...@fujitsu.com
Hello! \c is followed by [-reuse-previous=on/off] positional syntax | conninfo Using \c -reuse-previous=on positional syntax or \c positional syntax without -reuse-previous option, some parameters which were omitted or notated as "-" will be reused in the new connection. The target is only "dbna