Skip site navigation (1) Skip section navigation (2)

BUG #4815: max_connections setting has no impact

From: "Damien Guignard" <damien(dot)guignard(at)lotsys(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #4815: max_connections setting has no impact
Date: 2009-05-19 09:54:54
Message-ID: 200905190954.n4J9ssdF057913@wwwmaster.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugs
The following bug has been logged online:

Bug reference:      4815
Logged by:          Damien Guignard
Email address:      damien(dot)guignard(at)lotsys(dot)com
PostgreSQL version: 8.3.4
Operating system:   Windows
Description:        max_connections setting has no impact
Details: 

While testing connections i tried to raise up max_connections but this
setting is never taken into account. The maximum connection (backends from
pg_stat_database) seems to be the default number : 101.

Setting in postgresql.conf :
max_connections = 200

Commands to count connections in psql CLI :
show max_connections -> 200 (ok)
but stressed whith hundreds of connections :  
select sum(numbackends) from pg_stat_database; -> 101

Responses

pgsql-bugs by date

Next:From: Rainer BauerDate: 2009-05-19 12:24:25
Subject: Re: BUG #4815: max_connections setting has no impact
Previous:From: Heikki LinnakangasDate: 2009-05-19 08:32:59
Subject: Re: BUG #4812: statistics not available on tables containing only hstore column

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group