Skip to main content
NOT AVAILABLE IN SAAS.
To optimize PostgreSQL resource consumption for a Syteca deployment, generate tuned settings using the pgTune tool and apply them to the PostgreSQL server.
1

Open pgTune

Go to pgtune.leopard.in.ua.
2

Enter your hardware and database version

Fill in the form with the PostgreSQL server’s hardware specifications and PostgreSQL version.
For Number of Connections, enter at least the total number of Syteca Clients installed. If you have fewer than 100 Clients, this field can be left empty — the default maximum of 100 connections is already sufficient.
3

Generate the configuration

Click Generate and copy the resulting script.
4

Apply it to postgresql.conf

On the PostgreSQL server, open postgresql.conf (by default in C:\Program Files\PostgreSQL\<version>\data) and paste the script at the end of the file. Save.
5

Restart PostgreSQL

Restart the postgresql service to apply the changes.

​
Why connection count matters

Application Server opens a new PostgreSQL connection whenever a Client comes online, and either opens another connection or reuses the existing one whenever that Client starts a new live session, depending on what the database decides. A Client that’s online but not actively sending data may have its connection closed or kept open for future use. All manual requests made from the Management Tool (viewing the Audit log, generating reports, viewing sessions) share a single connection.
Terminal servers open one connection when the Client comes online, plus an additional connection for each user who logs in and starts a session — so terminal servers with many concurrent users need a correspondingly higher connection count.

​
Fix “53300: sorry, too many clients already”

NOT AVAILABLE IN SAAS.
This error appears in the logs when PostgreSQL’s maximum concurrent connection limit (100 by default) is reached. Application Server opens a new connection whenever a Client comes online, and either opens another or reuses the existing one whenever that Client starts a new session — terminal servers in particular open one connection per logged-in user, on top of the one opened when the terminal server’s Client itself comes online.
1

Stop the Application Server

Stop the EkranServer service.
2

Open postgresql.conf

On the PostgreSQL server, open the data folder (by default C:\Program Files\PostgreSQL\13\data) and open postgresql.conf.
3

Increase max_connections

Replace the default max_connections value of 100 with a higher value, for example 1000.
4

Save and restart PostgreSQL

Save the file, then restart the PostgreSQL service in Windows Services.
5

Restart the Application Server

Restart the EkranServer service.

​
Check database and table size

Creating databases manually

Manual PostgreSQL database and user setup.

Database requirements

Supported PostgreSQL versions and hardware sizing.

Database server errors

Common database connectivity issues and fixes.