TSPS : Multiple postgres processes are running and consuming memory

Version 1
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    TrueSight Presentation Server


    TSPS Server


    TSPS 10.x and 11.x


    TSPS : Multiple postgres processes are running and consuming memory


    Expected behavior


    PostgreSQL is process based, so it starts one Postgres instance per connection. The database starts a process for each connection, both from clients and from other server processes (Tomcat, etc.)  Despite the number of processes, they use very little in the way of real resources.

    The user, database, and connection source host items remain the same for the life of the client connection, but the activity indicator changes. The activity can be idle (i.e., waiting for a client command), idle in transaction (waiting for client inside a BEGIN block), or a command type name such as SELECT. Also, waiting is attached if the server process is presently waiting on a lock held by another server process.
    We have checked and confirmed internally that this is expected behaviour and shouldn’t be reason to worry.  

    Article Number:


    Article Type:

    Solutions to a Product Problem

      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles