The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications.
TypeScript aialternativeauthdatabasedenoembeddingsexamplefirebasenextjsoauth2pgvectorpostgispostgrespostgresqlpostgrestrealtimesupabasevectorswebsockets
fix(docs): repair internal content links (#51050)
Pamela Chia07c75e84fc3b
diff --git a/apps/docs/content/guides/ai/examples/huggingface-image-captioning.mdx b/apps/docs/content/guides/ai/examples/huggingface-image-captioning.mdxindex a0f89695d59..eca417fa5d3 100644--- a/apps/docs/content/guides/ai/examples/huggingface-image-captioning.mdx+++ b/apps/docs/content/guides/ai/examples/huggingface-image-captioning.mdx@@ -24,7 +24,7 @@ We can combine Hugging Face with [Supabase Storage](/storage) and [Database Webh- Create a `caption` column of type `text`.- Regenerate TypeScript types to include new `image_caption` table.- Deploy the function to Supabase: `supabase functions deploy huggingface-image-captioning`.-- Create the Database Webhook in the [Supabase Dashboard](/dashboard/project/_/database/hooks) to trigger the `huggingface-image-captioning` function anytime a record is added to the `storage.objects` table.+- Create the Database Webhook in the [Supabase Dashboard](/dashboard/project/_/integrations/webhooks/overview) to trigger the `huggingface-image-captioning` function anytime a record is added to the `storage.objects` table.## Generate TypeScript typesdiff --git a/apps/docs/content/guides/functions/examples/push-notifications.mdx b/apps/docs/content/guides/functions/examples/push-notifications.mdxindex 9787522b862..d340f8810b8 100644--- a/apps/docs/content/guides/functions/examples/push-notifications.mdx+++ b/apps/docs/content/guides/functions/examples/push-notifications.mdx@@ -271,7 +271,7 @@ Push notifications are an important part of any mobile app. They allow you to se## Create the database webhook- Navigate to the [Database Webhooks settings](/dashboard/project/_/database/hooks) in your Supabase Dashboard.+ Navigate to the [Database Webhooks settings](/dashboard/project/_/integrations/webhooks/overview) in your Supabase Dashboard.1. Enable and create a new hook.1. Conditions to fire webhook: Select the `public.notifications` table and tick the `Insert` event.diff --git a/apps/docs/content/guides/platform/manage-your-usage/logs-ingest.mdx b/apps/docs/content/guides/platform/manage-your-usage/logs-ingest.mdxindex e56527c9acd..e63fd4a1772 100644--- a/apps/docs/content/guides/platform/manage-your-usage/logs-ingest.mdx+++ b/apps/docs/content/guides/platform/manage-your-usage/logs-ingest.mdx@@ -48,15 +48,15 @@ Every service in your Supabase project generates logs automatically. Log volumeReduce the volume of a log type rather than turning it off completely. Raise a threshold rather than disabling logging outright as this prevents you from having information if something goes wrong later. For example a security incident or a slow query may be completely missed.-You change all of the Postgres settings below through [Custom Postgres Configuration](/guides/database/custom-postgres-config), either from the SQL Editor or the Supabase CLI. Some changes take effect immediately; others require a database restart. The CLI has a `--no-restart` option if you want to batch several changes together before restarting. See [Postgres log configuration](/guides/database/postgres/postgres-log-config) for the full list of configurable log settings and what each one does.+You change all of the Postgres settings below through [Custom Postgres Configuration](/docs/guides/database/custom-postgres-config), either from the SQL Editor or the Supabase CLI. Some changes take effect immediately; others require a database restart. The CLI has a `--no-restart` option if you want to batch several changes together before restarting. See [Postgres log configuration](/docs/guides/database/postgres/postgres-log-config) for the full list of configurable log settings and what each one does.### Start with the two biggest leversConsider these options first. They are responsible for most log volume on most projects.-- **[`log_statement`](/guides/database/postgres/postgres-log-config#logstatement)** — set to `none` if you don't manually read through raw query logs to debug your application, for example if your team relies on an AI coding assistant, an APM tool, or the Query Performance dashboard instead. Keep `all` on if you routinely read query text in the Logs Explorer to debug issues, or you have a compliance requirement to retain a full statement audit trail; `mod` is a lighter-volume option if you only need a record of data changes.-- **[`log_min_duration_statement`](/guides/database/postgres/postgres-log-config#logmindurationstatement)** — raise the threshold (for example, from a few milliseconds to 1-2 seconds) if you only care about queries that are slow enough to notice. Keep it low only while you're actively in a performance-tuning phase, and raise it back up once that investigation is done.-- **[pgAudit](/guides/database/extensions/pgaudit)**, if enabled — this extension can be very verbose independently of `log_statement`. Turn off a broad `pgaudit.log` or `pgaudit.role` configuration if you don't need a dedicated audit trail beyond what `log_statement` already gives you.+- **[`log_statement`](/docs/guides/database/postgres/postgres-log-config#logstatement)** — set to `none` if you don't manually read through raw query logs to debug your application, for example if your team relies on an AI coding assistant, an APM tool, or the Query Performance dashboard instead. Keep `all` on if you routinely read query text in the Logs Explorer to debug issues, or you have a compliance requirement to retain a full statement audit trail; `mod` is a lighter-volume option if you only need a record of data changes.+- **[`log_min_duration_statement`](/docs/guides/database/postgres/postgres-log-config#logmindurationstatement)** — raise the threshold (for example, from a few milliseconds to 1-2 seconds) if you only care about queries that are slow enough to notice. Keep it low only while you're actively in a performance-tuning phase, and raise it back up once that investigation is done.+- **[pgAudit](/docs/guides/database/extensions/pgaudit)**, if enabled — this extension can be very verbose independently of `log_statement`. Turn off a broad `pgaudit.log` or `pgaudit.role` configuration if you don't need a dedicated audit trail beyond what `log_statement` already gives you.<Admonition type="danger" title="Statement logs can expose sensitive data">@@ -66,20 +66,20 @@ Enabling `log_statement=all`, or setting `log_min_duration_statement` to a low o### Check these often-overlooked settings-- **[`log_connections` and `log_disconnections`](/guides/database/postgres/postgres-log-config#logconnections)** — turn off if you don't need a record of exactly when every connection opened and closed. Keep on if you're troubleshooting connection exhaustion or spikes, or have a security requirement to log all connection activity. If this setting is generating a lot of volume, your app may not be using a connection pooler such as Supavisor, which Supabase provides by default — connecting through the pooler reduces both log volume and the risk of running out of connections.-- **[`log_autovacuum_min_duration`](/guides/database/postgres/postgres-log-config#logautovacuumminduration)** — raise the threshold, or turn it off, if you're not actively diagnosing a table-maintenance problem. Keep it on with a reasonable threshold if you've had autovacuum-related performance issues before.-- **[`log_temp_files`](/guides/database/postgres/postgres-log-config#logtempfiles)** — turn off if you're not actively tuning query performance around memory usage. Keep it on if you're investigating slow queries related to sorting or joining large amounts of data.-- **[`log_lock_waits`](/guides/database/postgres/postgres-log-config#loglockwaits)** — turn off if you're not seeing symptoms of queries hanging. Keep it on if multiple processes write to the same data concurrently and you've seen unexplained slowdowns before.+- **[`log_connections` and `log_disconnections`](/docs/guides/database/postgres/postgres-log-config#logconnections)** — turn off if you don't need a record of exactly when every connection opened and closed. Keep on if you're troubleshooting connection exhaustion or spikes, or have a security requirement to log all connection activity. If this setting is generating a lot of volume, your app may not be using a connection pooler such as Supavisor, which Supabase provides by default — connecting through the pooler reduces both log volume and the risk of running out of connections.+- **[`log_autovacuum_min_duration`](/docs/guides/database/postgres/postgres-log-config#logautovacuumminduration)** — raise the threshold, or turn it off, if you're not actively diagnosing a table-maintenance problem. Keep it on with a reasonable threshold if you've had autovacuum-related performance issues before.+- **[`log_temp_files`](/docs/guides/database/postgres/postgres-log-config#logtempfiles)** — turn off if you're not actively tuning query performance around memory usage. Keep it on if you're investigating slow queries related to sorting or joining large amounts of data.+- **[`log_lock_waits`](/docs/guides/database/postgres/postgres-log-config#loglockwaits)** — turn off if you're not seeing symptoms of queries hanging. Keep it on if multiple processes write to the same data concurrently and you've seen unexplained slowdowns before.### Check this if your logs seem unusually large for no clear reason-**[`log_min_messages`](/guides/database/postgres/postgres-log-config#logminmessages)** controls the verbosity of Postgres's own internal logging, separate from query activity. The default is `warning`. If this was turned up to a debug level while troubleshooting a specific issue and never turned back down, it can produce a large, ongoing volume of internal messages that aren't useful for day-to-day monitoring — check the current value and reset it if you don't recognize turning it up yourself.+**[`log_min_messages`](/docs/guides/database/postgres/postgres-log-config#logminmessages)** controls the verbosity of Postgres's own internal logging, separate from query activity. The default is `warning`. If this was turned up to a debug level while troubleshooting a specific issue and never turned back down, it can produce a large, ongoing volume of internal messages that aren't useful for day-to-day monitoring — check the current value and reset it if you don't recognize turning it up yourself.Custom RPC functions and stored procedures are also worth reviewing. A PL/pgSQL function that calls `RAISE NOTICE` or `RAISE LOG` produces log output every time it runs, independent of any of the settings above — if a frequently-called function logs on every invocation, it can account for a large, otherwise-unexplained share of your volume.### Settings you can generally leave alone-[`log_checkpoints`](/guides/database/postgres/postgres-log-config#logcheckpoints), [`log_recovery_conflict_waits`](/guides/database/postgres/postgres-log-config#logrecoveryconflictwaits), `log_replication_commands`, and [`log_startup_progress_interval`](/guides/database/postgres/postgres-log-config#logstartupprogressinterval) are either low-volume by nature or only relevant if you use specific features such as replication. Unless you know you're using the related feature, these rarely contribute meaningfully to your total ingest.+[`log_checkpoints`](/docs/guides/database/postgres/postgres-log-config#logcheckpoints), [`log_recovery_conflict_waits`](/docs/guides/database/postgres/postgres-log-config#logrecoveryconflictwaits), `log_replication_commands`, and [`log_startup_progress_interval`](/docs/guides/database/postgres/postgres-log-config#logstartupprogressinterval) are either low-volume by nature or only relevant if you use specific features such as replication. Unless you know you're using the related feature, these rarely contribute meaningfully to your total ingest.## Checking your new usage baselinediff --git a/apps/docs/content/guides/platform/migrating-within-supabase/backup-restore.mdx b/apps/docs/content/guides/platform/migrating-within-supabase/backup-restore.mdxindex 43b00dd9ee7..f43342613f3 100644--- a/apps/docs/content/guides/platform/migrating-within-supabase/backup-restore.mdx+++ b/apps/docs/content/guides/platform/migrating-within-supabase/backup-restore.mdx@@ -107,7 +107,7 @@ These steps cover a manual logical restore (`pg_dump` / `psql`) into a project y<StepHikeCompact.Details title="Configure newly created project" fullWidth>In the new project:- - If Webhooks were used in the old database, enable [Database Webhooks](/dashboard/project/_/database/hooks).+ - If Webhooks were used in the old database, enable [Database Webhooks](/dashboard/project/_/integrations/webhooks/overview).- If any non-default extensions were used in the old database, enable the [Extensions](/dashboard/project/_/database/extensions).</StepHikeCompact.Details>diff --git a/apps/docs/content/guides/platform/migrating-within-supabase/dashboard-restore.mdx b/apps/docs/content/guides/platform/migrating-within-supabase/dashboard-restore.mdxindex 0da67357ab3..b3f4b646aac 100644--- a/apps/docs/content/guides/platform/migrating-within-supabase/dashboard-restore.mdx+++ b/apps/docs/content/guides/platform/migrating-within-supabase/dashboard-restore.mdx@@ -39,7 +39,7 @@ Dashboard backups are only available for older projects that still use logical b<StepHikeCompact.Details title="Configure your new project" fullWidth>In your new project:- - If you were using Webhooks, enable [Database Webhooks](/dashboard/project/_/database/hooks).+ - If you were using Webhooks, enable [Database Webhooks](/dashboard/project/_/integrations/webhooks/overview).- If you were using any extensions, enable the [Extensions](/dashboard/project/_/database/extensions).- If you were using Replication for Realtime, enable [Publication](/dashboard/project/_/database/publications) where needed.</StepHikeCompact.Details>diff --git a/apps/docs/content/troubleshooting/webhook-debugging-guide-M8sk47.mdx b/apps/docs/content/troubleshooting/webhook-debugging-guide-M8sk47.mdxindex c871926220c..c9c5042eea1 100644--- a/apps/docs/content/troubleshooting/webhook-debugging-guide-M8sk47.mdx+++ b/apps/docs/content/troubleshooting/webhook-debugging-guide-M8sk47.mdx@@ -43,7 +43,7 @@ Go to your [Table Editor](/dashboard/project/_/editor/) and navigate to the netThe `_http_response` table saves all the response messages from the past 6 hours. If every column contains NULL values, except for the `id`, `error_msg`, and `created` columns, then you are experiencing [a timeout bug](https://github.com/supabase/pg_net/issues/86).-By default, webhooks will execute the next 200 available queued requests. If the requests are too intense, it may result in a mass timeout. In the [Webhook Dashboard](/dashboard/project/_/database/hooks), you should increase your webhook's timeout to minimize this issue.+By default, webhooks will execute the next 200 available queued requests. If the requests are too intense, it may result in a mass timeout. In the [Webhook Dashboard](/dashboard/project/_/integrations/webhooks/overview), you should increase your webhook's timeout to minimize this issue.**4. Inspect endpoints**The below code makes a request to the Postman Echo API through PG_NET