HI Andreas, thanks for your replay, i have checked connection number for the last 3 mouths and maximum number of connection was 300, so i can reduce this is it's cousin the issue. during this error server was 99% idle, the only thing is that there was a pg_dump running on one of the DB, can this cause this error, also i have restarted pg server 2 days before because of server cert update.
Thanks. ----- Original Message ----- From: "Andreas Kretschmer" <akretsch...@spamfence.net> To: pgsql-performance@postgresql.org Sent: Wednesday, January 4, 2017 11:12:23 AM Subject: Re: [PERFORM] Unable to connect to server Vucomir Ianculov <vuko...@os-ux.com> wrote: > Hi, > > today i head a issue with pgsql 9.3, a lot of clients complained that they > are > unable to connect to the server. > when i have checked the logs i sow a lot of > FATAL: canceling authentication due to timeout you can increase authentication_timeout, default is 1 minute. How many clients do you have, do you really needs 1000 connections? If yes, please consider a connection pooler like pgbouncer. Regards, Andreas Kretschmer -- Andreas Kretschmer http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
