From: | 林俊彥 <james(dot)lin(at)cenoq(dot)com> |
---|---|
To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
Cc: | Pg Bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: [Bug / Question ] " authentication_timeout " is invalid. |
Date: | 2015-09-17 04:02:02 |
Message-ID: | CAGRvhK2a+8bcY7pAZy47Ke=Tn99Vhgw1GJ=pEWgojEroqiLa4A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hi , Jeff,
Thank you for reply. I used to use in the following ways but still
could not be verified:
----------- Log start ---------------------
[BEGIN] 2015/9/17 11:51:51
[postgres(at)pg95 ~]$ cat test.sh
#!/bin/bash
ip a |grep eth0
psql -h 100.200.100.211<<EOF
show authentication_timeout;
select now();
\! sh net_test.sh
select now();
EOF
[postgres(at)pg95 ~]$ cat net_test.sh
#!/bin/bash
sudo ifdown eth0
sleep 90
sudo ifup eth0
[postgres(at)pg95 ~]$ ./test.sh
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfif
o_fast state UP qlen 1000
inet 100.200.100.211/8 brd 100.255.255.255 scope global eth0
authentication_timeout
------------------------
1min
(1 row)
now
-------------------------------
2015-09-17 11:52:43.842508+08
(1 row)
now
-------------------------------
2015-09-17 11:54:18.161079+08
(1 row)
[END] 2015/9/17 11:54:35
----------- Log end ----------------------
Could you give me an example to verify it? Let me verify it is active or
not. thank you !!
best regards,
James
2015-09-16 23:52 GMT+08:00 Jeff Janes <jeff(dot)janes(at)gmail(dot)com>:
> On Wed, Sep 16, 2015 at 3:27 AM, 林俊彥 <james(dot)lin(at)cenoq(dot)com> wrote:
>
>> Hi, sir,
>>
>> the "postgresql.conf" 's "authentication_timeout" is not active.
>>
>> The Log:
>>
>> -------------------------------------------------------------------------------------------------
>> [BEGIN] 2015/9/16 17:57:37
>> [postgres(at)pg95 ~]$ psql -V
>> psql (PostgreSQL) 9.5alpha2
>> [postgres(at)pg95 ~]$ time psql -c 'show authentication_timeout ;'
>> Password:
>> authentication_timeout
>> ------------------------
>> 1min
>> (1 row)
>> real 4m39.528s
>> user 0m0.003s
>> sys 0m0.002s
>>
>> [END] 2015/9/16 18:03:10
>>
>> ---------------------------------------------------------------------------------------------------
>> The document is said :
>> From:
>>
>> http://www.postgresql.org/docs/9.4/static/runtime-config-connection.html
>>
>> authentication_timeout (integer)
>>
>> Maximum time to complete client authentication, in seconds. If a would-be
>> client has not completed the authentication protocol in this much time, the
>> server closes the connection. This prevents hung clients from occupying a
>> connection indefinitely. The default is one minute (1m). This parameter
>> can only be set in the postgresql.conf file or on the server command
>> line.
>>
>> I can't find about this information or solution by goolge search or forum,
>> Please tell me how to verify it is active . or check it running?
>>
>
> What happens behind the scenes is that psql first tries to connect without
> a password. It is told that it can't connect without a password. It
> closes the uncompleted connection. Then psql asks you for a password,
> waits until you enter one, and then starts a new connection using the
> password. So during the wait time, there is no pending connection to the
> database to be timed out. It is the client program psql which is doing the
> waiting, not the database server.
>
> Cheers,
>
> Jeff
>
From | Date | Subject | |
---|---|---|---|
Next Message | mikael.krantz | 2015-09-17 09:49:02 | BUG #13624: App shutdown due to fatal error, and want start after that |
Previous Message | Tom Lane | 2015-09-17 03:48:48 | Re: BUG #13622: unsafe use of relative rpath libpq.5.dylib |