From f08521ed56b0e33f919eecbd4ebf116a03a70eb4 Mon Sep 17 00:00:00 2001 From: Steve Chavez Date: Mon, 12 Jun 2023 11:16:42 -0500 Subject: [PATCH] Add connection pool link in Serverless API Adds a link to the PostgREST connection pool docs --- apps/docs/pages/guides/database/connecting-to-postgres.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/docs/pages/guides/database/connecting-to-postgres.mdx b/apps/docs/pages/guides/database/connecting-to-postgres.mdx index d5b067f14c0..c48c8bba747 100644 --- a/apps/docs/pages/guides/database/connecting-to-postgres.mdx +++ b/apps/docs/pages/guides/database/connecting-to-postgres.mdx @@ -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.