Thread: [BUGS] BUG #14708: Frequent connection timeout issue while connecting toPostgres database
[BUGS] BUG #14708: Frequent connection timeout issue while connecting toPostgres database
From
ruchitat@planittesting.com
Date:
The following bug has been logged on the website: Bug reference: 14708 Logged by: Ruchita Terse Email address: ruchitat@planittesting.com PostgreSQL version: 9.6.1 Operating system: Windows Description: In our database setup we are often encounter wiht the connection timeout issue while connecting with external application. Please find the detailed information below. While server trying to connect Postgres database we are getting following error message : 1. FATAL: cancelling authentication due to timeout. 2. FATAL : two many clients already. Even the number of actual connected clients is very minimum. The maximum limit set for connection of clients is 200 and also currently utilized connections are not more than 50 i.e not exceeding default connection limit. PS: We are connecting with port 5432 Kindly help us to resolve this issue. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #14708: Frequent connection timeout issue whileconnecting to Postgres database
From
Michael Paquier
Date:
On Thu, Jun 15, 2017 at 8:14 PM, <ruchitat@planittesting.com> wrote: > While server trying to connect Postgres database we are getting following > error message : > 1. FATAL: cancelling authentication due to timeout. > 2. FATAL : two many clients already. Those are not error strings present in the source code. Those two are though: "canceling authentication due to timeout" "sorry, too many clients already" > Even the number of actual connected clients is very minimum. The > maximum limit set for connection of clients is 200 and also currently > utilized connections are not more than 50 i.e not exceeding default > connection limit. Are you sure that there are not connection attempt spikes? log_connections = on would help in checking incoming connection attempts. > Kindly help us to resolve this issue. I am not seeing any direct bugs here but... The "due to timeout" message comes from ProcessInterrupts(), which refers to the fact that the process is being shut down. So shouldn't this message be changed? The current message looks confusing to me. Please see the attached. -- Michael -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs