dima/supabase
1
0 Fork 0
mirror of https://github.com/supabase/supabase.git synced 2026-10-05 09:25:06 +03:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #14982 from supabase/connection-pool

Browse Source 
Add connection pool link in Serverless API
This commit is contained in:
Greg Richardson authored and GitHub committed 2023-06-12 11:25:46 -06:00
2 parents 7f96105fc5 f08521ed56
commit 2568bfcb7d
1 file changed
+1 -1
Download Patch File Download Diff File Expand all files Collapse all files
apps/docs/pages/guides/database/connecting-to-postgres.mdx
+1 -1
View File
@@ -53,7 +53,7 @@ Every Supabase project comes with PgBouncer for connection pooling. A connection
## Choosing a connection method
- The Serverless APIs provide programmatic access and have built-in connection pooling. You can use these for all browser and application interactions. We recommend using these wherever possible.
- The Serverless APIs provide programmatic access and have [built-in connection pooling](https://postgrest.org/en/stable/references/connection_pool.html). You can use these for all browser and application interactions. We recommend using these wherever possible.
- A "direct connection" is Postgres' native connection system. You should use this for tools which are always alive - usually installed on a long-running server, like Node.js, Ruby, Python, etc.
- A "connection pooler" is a tool which keeps connections "alive". You should use this for serverless functions and tools which disconnect from the database frequently, like Prisma, Drizzle, Kysely, etc.