lywsvip/supabase
1
0
Fork 0
mirror of https://github.com/supabase/supabase.git synced 2026-05-07 06:27:16 +08:00
Code Issues Packages Projects Releases Wiki Activity

[bot] fix lint errors (#32892)

Browse Source 
Co-authored-by: github-docs-bot <github-docs-bot@supabase.com>
This commit is contained in:
github-actions[bot]
2025-01-18 01:45:26 +00:00
committed by GitHub
parent c2ece15f22
commit 9742de2ab2
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
apps/docs/content/troubleshooting/how-to-change-max-database-connections-_BQ8P5.mdx
View File

@@ -12,7 +12,7 @@ cli = [ "supabase-postgres-config-update" ]
> WARNING: Manually configuring the connection count hard codes it. This means if you upgrade or downgrade your database, the connection count will not auto-resize. You will have to make sure to manually update it.
# Changing Max Database Connections:
# Changing max database connections:
Each compute instance has a default direct connection and pooler connection settings. You can find the most recent settings in the [compute docs](https://supabase.com/docs/guides/platform/compute-add-ons#disk-io):
@@ -30,7 +30,7 @@ Each compute instance has a default direct connection and pooler connection sett
| 12XL | 500 | 9,000 |
| 16XL | 500 | 12,000 |
## Configuring Direct Connections Limits
## Configuring direct connections limits
> Note: the Supavisor connection limits are hard-coded and cannot be changed without upgrading the compute size:
@@ -54,7 +54,7 @@ SHOW max_connections;
**Three** factors must be taken into consideration when adjusting the direct connection limit:
### Process Schedulers and Postgres Internals:
### Process schedulers and Postgres internals:
Allowing too many direct connections in your database can overburden Postgres schedulers and other internal modules. This will result in a noticeable decrease in query throughput, despite having more connections available. EnterpriseDB wrote a wonderful [article](https://www.enterprisedb.com/postgres-tutorials/why-you-should-use-connection-pooling-when-setting-maxconnections-postgres) that outlines some of the considerations.