Hi @sydhub16934284,

To address the issues with Pega's idle connections not being cleared and the duplicate insert queries in PostgreSQL, you can adjust the connection pool settings in Pega and potentially configure PostgreSQL to handle these issues more efficiently. Here are some recommended steps and settings:

1. Adjust Pega Connection Pool Settings

• Max Connections: Configure the maximum number of connections Pega can open to PostgreSQL. This should be set based on your application's concurrency needs and PostgreSQL's capacity.
• Idle Timeout: Set a timeout period after which idle connections are closed to prevent them from accumulating. This helps in releasing resources and reducing memory usage.
• Connection Validation: Enable validation of connections before they are returned to the pool to avoid returning stale or invalid connections.
• Configure PostgreSQL
• Connection Settings: Ensure PostgreSQL's max_connections parameter is set appropriately to handle the maximum number of connections from Pega.
• Connection Pooling: Consider using a connection pooling mechanism like PgBouncer or configuring PostgreSQL's built-in connection pooling parameters (pgpool) to manage connections more efficiently.
• Monitoring and Logging: Monitor PostgreSQL's logs for any clues about duplicate insert queries. Consider enabling logging of SQL statements to identify and debug these queries.

Hope it helps

Regards

Raja