feat(studio): add pgbouncer description to query perf

[kemaldotearth]

I have read the CONTRIBUTING.md file.

YES

What kind of change does this PR introduce?

This was missing for queries that still use pgbouncer as a role. I know it's deprecated, so I put the same message that we have on the blog post here.

Fixes this:

cc @jordienr who found the bug.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
studio-self-hosted	Ready	Preview	Comment	Sep 29, 2025 8:01am
studio-staging	Ready	Preview	Comment	Sep 29, 2025 8:01am

6 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
cms	Ignored			Sep 29, 2025 8:01am
studio	Ignored			Sep 29, 2025 8:01am
design-system	Skipped			Sep 29, 2025 8:01am
docs	Skipped			Sep 29, 2025 8:01am
ui-library	Skipped			Sep 29, 2025 8:01am
zone-www-dot-com	Skipped			Sep 29, 2025 8:01am

[supabase]

This pull request has been ignored for the connected project xguihxuzqibwxjnimxev because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

[coveralls]

coverage: 69.874%. remained the same
when pulling 3b14fb7 on feat/add-pgbouncer-description-query-perf
into 1973615 on master.

[kevcodez]

PgBouncer is not deprecated, quite the opposite - it's our recommended, dedicated pooler for any paid organization. Caveat is only available on paid plans + only supports IPv6

Supavisor is the shared pooler that should only be used on the Free Plan or if you're not in a ipv6 compatible environment

[kemaldotearth]

PgBouncer is not deprecated, quite the opposite - it's our recommended, dedicated pooler for any paid organization. Caveat is only available on paid plans + only supports IPv6

Supavisor is the shared pooler that should only be used on the Free Plan or if you're not in a ipv6 compatible environment

@kevcodez cheers for clearing that up, what would you suggest writing there? Is there a more generic description of pgbouncer we can use? Maybe we can say something like:

PgBouncer is a lightweight connection pooler for PostgreSQL. Paid plans only.