FeatureFuel
2

Feature Request: Expose Database Pooler Connection Details via Environment Variable

Source: supabase/supabase#33089 · opened by @solistico770
Hi Supabase Team,

To simplify working with connection pooling, could we add a SUPABASE_DB_POOLER_URL environment variable?

Problem:
The pooler URL includes dynamic regional components (e.g., aws-0-eu-central-1.pooler.supabase.com), which developers currently have to hardcode or fetch manually via the API. For example:


postgresql://postgres.[project-id]:[YOUR-PASSWORD]@aws-0-eu-central-1.pooler.supabase.com:6543/postgres
The aws-0-eu-central-1 region prefix is unpredictable and varies across projects.

Request:
Expose the full pooler connection string via an environment variable like SUPABASE_DB_POOLER_URL.

Benefits:

Avoids hardcoding region-specific pooler addresses.

Matches the existing SUPABASE_DB_URL pattern for consistency.

Simplifies configuration for pooled connections in serverless/edge environments.

Reduces API calls for teams scaling across regions.

Thank you for considering this! 🙌

No pledges yet. Be the first to back this.

Make a pledge

Pledge your monetary support if this feature is added.

$

Comments

No comments yet.

Replying to

Add a comment

What do you think about this feature request?


Similar requests