The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications.
TypeScript aialternativeauthdatabasedenoembeddingsexamplefirebasenextjsoauth2pgvectorpostgispostgrespostgresqlpostgrestrealtimesupabasevectorswebsockets
docs: fix broken internal links in database and telemetry guides (#46569)
Sebeen Kwonab106f6110b4
diff --git a/apps/docs/content/guides/database/postgres/data-deletion.mdx b/apps/docs/content/guides/database/postgres/data-deletion.mdxindex 685dcc44f80..a8a0941bbdd 100644--- a/apps/docs/content/guides/database/postgres/data-deletion.mdx+++ b/apps/docs/content/guides/database/postgres/data-deletion.mdx@@ -202,4 +202,4 @@ The most efficient way to reclaim disk space, without locks, is to use [pg_repac- [Safe Cascading Deletes](/docs/guides/database/postgres/cascade-deletes)- [Inspecting your Database](/docs/guides/database/inspect)- [Understanding Database and Disk Size](/docs/guides/platform/database-size)-- [Bloat in Postgres](/docs/blog/postgres-bloat)+- [Bloat in Postgres](/blog/postgres-bloat)diff --git a/apps/docs/content/guides/database/prisma.mdx b/apps/docs/content/guides/database/prisma.mdxindex b72c2f8294f..ad89d25702d 100644--- a/apps/docs/content/guides/database/prisma.mdx+++ b/apps/docs/content/guides/database/prisma.mdx@@ -414,7 +414,7 @@ If you plan to solely use Prisma instead of the Supabase Data API (PostgREST), t```<Admonition type="note" title="conflict management">- If there are any conflicts, reference [Prisma's official doc](https://www.prisma.io/docs/orm/prisma-migrate/getting-started#work-around-features-not-supported-by-prisma-schema-language) or the [trouble shooting guide](/docs/guides/database/prisma-troubleshooting) for more details+ If there are any conflicts, reference [Prisma's official doc](https://www.prisma.io/docs/orm/prisma-migrate/getting-started#work-around-features-not-supported-by-prisma-schema-language) or the [trouble shooting guide](/docs/guides/database/prisma/prisma-troubleshooting) for more details</Admonition>diff --git a/apps/docs/content/guides/telemetry/reports.mdx b/apps/docs/content/guides/telemetry/reports.mdxindex 88ed4668c23..ce1cab60acf 100644--- a/apps/docs/content/guides/telemetry/reports.mdx+++ b/apps/docs/content/guides/telemetry/reports.mdx@@ -133,7 +133,7 @@ Actions you can take:| Action | Description || --------------------------------------------------------------------------- | ---------------------------------------------- || [Upgrade compute size](/docs/guides/platform/compute-and-disk#compute-size) | Increase available memory resources |-| [Optimize queries](/docs/content/guides/database/query-optimization) | Reduce memory consumption of expensive queries |+| [Optimize queries](/docs/guides/database/query-optimization) | Reduce memory consumption of expensive queries || [Tune Postgres configuration](https://pgtune.leopard.in.ua) | Improve memory management settings || Implement application caching | Add query result caching to reduce memory load |@@ -169,12 +169,12 @@ How it helps debug issues:Actions you can take:-| Action | Description |-| ---------------------------------------------------------------------------------- | ----------------------------------------------- |-| [Optimize CPU-intensive queries](/docs/content/guides/database/query-optimization) | Target queries causing high User CPU usage |-| Address IO bottlenecks | Resolve disk/network issues when IOWait is high |-| [Upgrade compute size](/docs/guides/platform/compute-and-disk) | Increase available CPU capacity |-| [Implement proper indexing](/docs/guides/database/postgres/indexes) | Use query optimization techniques |+| Action | Description |+| -------------------------------------------------------------------------- | ----------------------------------------------- |+| [Optimize CPU-intensive queries](/docs/guides/database/query-optimization) | Target queries causing high User CPU usage |+| Address IO bottlenecks | Resolve disk/network issues when IOWait is high |+| [Upgrade compute size](/docs/guides/platform/compute-and-disk) | Increase available CPU capacity |+| [Implement proper indexing](/docs/guides/database/postgres/indexes) | Use query optimization techniques |### Disk input/output operations per second (IOPS)@@ -227,7 +227,7 @@ Actions you can take:| Action | Description || ------------------------------------------------------------------------------------ | ------------------------------------------------------------- |-| [Optimize disk-intensive queries](/docs/content/guides/database/query-optimization) | Reduce queries that perform excessive reads/writes |+| [Optimize disk-intensive queries](/docs/guides/database/query-optimization) | Reduce queries that perform excessive reads/writes || Tune caching and batching | Minimize repeated disk access and improve throughput headroom || [Upgrade compute size](/docs/guides/platform/compute-and-disk) | Increase throughput limits for sustained workloads || Review database design | Optimize schema and query patterns for efficiency |