Thank you Adrian. Yes, I confirm that all the databases are running in one PostgreSQL server/instance. I'm running this version: PostgreSQL 9.3.15 on i686-pc-linux-gnu, compiled by gcc (Ubuntu 4.8.4-2ubuntu1~14.04.3) 4.8.4, 32-bit Let me ask: is there a way to monitor the total connections to postgresql through time? Or should I make my own script for that? I ask because every time the error is thrown, I check the total connections with "select count(*) from pg_stat_activity;" but the number is always far from the configured max_connections. Maybe the problem is with pgBouncer, so I'll post this issue in their forum. I'm not really a sysop, so it's hard for me to fully understand the issue. The strange part is that the error appears in random hours, I mean, it doesn't correspond with the hours of higher db activity. Instead, the error appears in both scenarios: with high db activity and with very low db activity. For example, early this morning in postgresql log: 2017-02-28 06:26:33 GMT FATAL: remaining connection slots are reserved for non-replication superuser connections 2017-02-28 06:26:48 GMT FATAL: remaining connection slots are reserved for non-replication superuser connections 2017-02-28 06:26:50 GMT FATAL: remaining connection slots are reserved for non-replication superuser connections 2017-02-28 06:26:50 GMT FATAL: remaining connection slots are reserved for non-replication superuser connections And in pgbouncer log: 2017-02-28 06:26:39.035 4080 LOG Stats: 7 req/s, in 322589 b/s, out 2281293 b/s,query 307926 us 2017-02-28 06:27:31.510 4080 ERROR S: login failed: FATAL: remaining connection slots are reserved for non-replication superuser connections 2017-02-28 06:27:32.511 4080 ERROR S: login failed: FATAL: remaining connection slots are reserved for non-replication superuser connections 2017-02-28 06:27:32.511 4080 ERROR S: login failed: FATAL: remaining connection slots are reserved for non-replication superuser connections 2017-02-28 06:27:32.514 4080 ERROR S: login failed: FATAL: remaining connection slots are reserved for non-replication superuser connections 2017-02-28 06:27:39.036 4080 LOG Stats: 10 req/s, in 334173 b/s, out 2187475 b/s,query 220037 us 2017-02-28 06:28:39.036 4080 LOG Stats: 7 req/s, in 335683 b/s, out 2287722 b/s,query 370778 us 2017-02-28 06:28:46.595 4080 WARNING C-0x8d56390: radionew/medios@127.0.0.1:40910 Pooler Error: pgbouncer cannot connect to server 2017-02-28 06:29:39.037 4080 LOG Stats: 7 req/s, in 275963 b/s, out 1976669 b/s,query 261484 us Anyway, I'll post a thread in the pgBouncer forum. I'll search for some tool to monitor the total number of postgresql connections through time. Any comment or suggestion will be appreciated. Thank you very much for your time! Best regards, Lisandro. -- View this message in context: http://www.postgresql-archive.org/GMT-FATAL-remaining-connection-slots-are-reserved-for-non-replication-superuser-connections-but-I-m-g-tp5946245p5946775.html Sent from the PostgreSQL - general mailing list archive at Nabble.com. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
