Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.Join Us
In a very busy environment running Qlik Sense server, the Windows Task Manager may show too many instances or postgres.exe running simultaneously. This is normal.
The sympton here is related to the number of connections to the database.
On starting Postgres database, it is normal to find many instances of postgres.exe listed in Windows Task Manager.
PostgreSQL is process based, so it starts one postgres.exe on Windows instance per connection.
It is normal to see many instances of postgres.exe listed in Windows Task Manager.
PostgreSQL uses a multi-process architecture. In an empty system you will see anything from two to five processes. Once clients start to connect, the number of processes will increase.
The idea behind this seems to be that if a process dies, it won’t take all other processes with it. To avoid if one thread crashes which would then cause the whole application to crash.
Look at reducing the number of connections, if possible.
For example separating development, testing and production into separate environments, with a separate repository database for each instead of combined database
Search Qlik's Support Knowledge database or request assisted support for highly complex issues.Submit a case
Experiencing a serious issue, please contact us by phone. View phone numbers and hours by region.