# LinuxOne s390 Postgresql 15.1 Max\_Connection Limit

**URL:** <https://forums.percona.com/t/linuxone-s390-postgresql-15-1-max-connection-limit/22091>\
**Category:** PostgreSQL\
**Created:** [May 16, 2023, 6:59pm UTC](https://forums.percona.com/t/linuxone-s390-postgresql-15-1-max-connection-limit/22091 "2023-05-16T18:59:54Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![parttime](https://avatars.discourse-cdn.com/v4/letter/p/bcef8e/32.png) [@parttime](https://forums.percona.com/u/parttime)\
**Post date:** [May 16, 2023, 6:59pm UTC](https://forums.percona.com/t/linuxone-s390-postgresql-15-1-max-connection-limit/22091/1 "2023-05-16T18:59:55Z")

</div>

Hi,  
We have postgresql database 15.1 is running on the LinuxOne s390. High avalibility is provided wtih Patroni. When we try to increase the max\_connection, we get error.  
First we increased it from 100 to 500 and it was succesfull. But max connection from 500 to 1000 we get error.  
How we solve this problem?

---

<div class="post-metadata">

**Author:** ![Robert\_Bernier](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/robert_bernier/32/1367_2.png) [@Robert\_Bernier](https://forums.percona.com/u/Robert_Bernier)\
**Post date:** [May 16, 2023, 7:23pm UTC](https://forums.percona.com/t/linuxone-s390-postgresql-15-1-max-connection-limit/22091/2 "2023-05-16T19:23:04Z")

</div>

Hi,

So I’ve done the easy thing and copied and pasted the relevant parts from the Patroni [documentation](https://patroni.readthedocs.io/en/latest/dynamic_configuration.html)

“How” you go about increasing the parameter, especially with Patroni, is relevant.

> DYNAMIC CONFIGURATION  
> patronictl -c /etc/patroni/patroni.yml edit-config

> Dynamic configuration.  
> These options can be set in DCS at any time. If the options changed are not part of the startup configuration, they are applied asynchronously (upon the next wake up cycle) to every node, which gets subsequently reloaded. If the node requires a restart to apply the configuration (for options with context postmaster, if their values have changed), a special flag, pending\_restart indicating this, is set in the members.data JSON. Additionally, the node status also indicates this, by showing “restart\_pending”: true.

> Some of the PostgreSQL parameters must hold the same values on the primary and the replicas. For those, values set either in the local patroni configuration files or via the environment variables take no effect. To alter or set their values one must change the shared configuration in the DCS. Below is the actual list of such parameters together with the default values:
> 
> max\_connections: 100  
> max\_locks\_per\_transaction: 64  
> max\_worker\_processes: 8  
> max\_prepared\_transactions: 0  
> wal\_level: hot\_standby  
> wal\_log\_hints: on  
> track\_commit\_timestamp: off

Hope this helps.

Robert

---

<div class="post-metadata">

**Author:** ![parttime](https://avatars.discourse-cdn.com/v4/letter/p/bcef8e/32.png) [@parttime](https://forums.percona.com/u/parttime)\
**Post date:** [June 6, 2023, 7:23pm UTC](https://forums.percona.com/t/linuxone-s390-postgresql-15-1-max-connection-limit/22091/3 "2023-06-06T19:23:22Z")

</div>

thanks for your response.  
We solved this problem. pg\_stat\_statment extension must update version.