Integrate pgBouncer with PostgreSQL for Built-In Connection Pooling

[haysquareA]

I would like to request the integration of pgBouncer directly into the PostgreSQL service provided by Coolify. Adding built‑in connection pooling would simplify the setup for users and improve database performance in high‑concurrency environments without requiring manual deployment of a separate pgBouncer container.

Rationale:

Simplified Setup:
Many users rely on Coolify for a streamlined experience. An integrated pgBouncer would eliminate the need for a separate configuration and reduce deployment complexity.
Performance Improvements:
Built‑in connection pooling can reduce connection overhead and improve the overall responsiveness of the database, especially under high load.
Configuration Flexibility:
Allowing users to enable or disable pgBouncer and configure its parameters (e.g., pool mode, pool size, max connections) through environment variables or a configuration file would provide granular control tailored to different deployment scenarios.
Request Details:

Integration Approach:
Add pgBouncer as a built‑in component within the PostgreSQL container or as an optional service that can be toggled via configuration.
Configuration Options:
Provide environment variables or configuration settings to:
Enable or disable pgBouncer.
Set key pooling parameters such as pool mode (transaction, session, statement), default pool size, and maximum client connections.