mirror of
https://github.com/supabase/supabase.git
synced 2026-10-06 09:55:06 +03:00
Adds another connection for clarity
This commit is contained in:
1 parent
0fe0b63bc9
commit
454946a9c8
1 file changed
+10
-4
@@ -4,12 +4,18 @@ title: "Overview"
|
||||
description: There are various ways to connect to your Postgres database.
|
||||
---
|
||||
|
||||
Supabase provides two options for connection to your Postgres database:
|
||||
Supabase provides several options for connection to your Postgres database:
|
||||
|
||||
- Direct connections.
|
||||
- Connection pooling, using PgBouncer.
|
||||
- HTTP connections using the API.
|
||||
- Direct connections using Postgres' standard connection system.
|
||||
- Connection pooling using PgBouncer.
|
||||
|
||||
## Direct connection vs Connection Pooling
|
||||
## HTTP
|
||||
|
||||
Supabase provides an auto-updating API. This is the easiest way to get started if you are managing data (fetching, inserting, updating). However you cannot manage the database schema
|
||||
via the API (for security reasons). To do that you can either use the dashboard we provide or connect directly to your database.
|
||||
|
||||
## Direct vs Connection Pooling
|
||||
|
||||
A "direct connection" is when a connection is made to the database using Postgres' native connection implementation.
|
||||
|
||||
|
||||
Reference in new issue
Block a user