From 4d492db5eb9d8d36ad5d1c1b2a9f444b47a2cee1 Mon Sep 17 00:00:00 2001
From: Maksym Ionutsa <123338468+peekknuf@users.noreply.github.com>
Date: Thu, 13 Aug 2026 22:38:04 +0200
Subject: [PATCH] docs: update settings links after upgrade UI move to General
(#49053)
## I have read the
[CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md)
file.
YES
## What kind of change does this PR introduce?
docs update
- Upgrade project button and Postgres/PostgREST version checks moved
from Infrastructure to General settings
- Updated links across 13 docs pages to match
## Summary by CodeRabbit
- **Documentation**
- Updated dashboard links throughout the documentation to direct users
to **General Settings** instead of **Infrastructure Settings**.
- Corrected guidance for Postgres, pgvector, pg_net, and PostgREST
upgrades, configuration, and version checks.
- Updated monitoring, Grafana, and Log Drains links to current
documentation paths.
- Fixed troubleshooting links, CLI project path examples, pg_cron
terminology, and Markdown formatting.
---
apps/docs/content/guides/ai/vector-indexes.mdx | 2 +-
.../content/guides/ai/vector-indexes/hnsw-indexes.mdx | 2 +-
.../content/guides/api/rest/postgrest-error-codes.mdx | 2 +-
apps/docs/content/guides/api/securing-your-api.mdx | 2 +-
apps/docs/content/guides/database/extensions.mdx | 2 +-
.../docs/content/guides/database/extensions/pg_net.mdx | 2 +-
apps/docs/content/guides/getting-started/features.mdx | 2 +-
.../metrics/grafana-self-hosted.mdx | 2 +-
apps/docs/content/guides/platform/billing-faq.mdx | 2 +-
.../content/guides/platform/network-restrictions.mdx | 2 +-
apps/docs/content/guides/platform/project-transfer.mdx | 2 +-
apps/docs/content/guides/platform/temporary-access.mdx | 2 +-
apps/docs/content/guides/platform/upgrading.mdx | 4 ++--
.../forbidden-resource-error-from-the-cli-L6rm6l.mdx | 2 +-
.../grafana-not-displaying-data-sXJrMj.mdx | 2 +-
...-lookup-speeds-by-applying-an-hsnw-index-ohLHUM.mdx | 2 +-
...interpreting-supabase-grafana-cpu-charts-9JSlkC.mdx | 2 +-
.../troubleshooting/pgcron-debugging-guide-n1KTaz.mdx | 10 +++++-----
...n-does-not-exist-when-using-or-operators-46ff23.mdx | 4 ++--
.../rls-performance-and-best-practices-Z5Jjwv.mdx | 2 +-
.../troubleshooting/webhook-debugging-guide-M8sk47.mdx | 4 ++--
21 files changed, 28 insertions(+), 28 deletions(-)
diff --git a/apps/docs/content/guides/ai/vector-indexes.mdx b/apps/docs/content/guides/ai/vector-indexes.mdx
index 99f1d8823b1..08488384a2f 100644
--- a/apps/docs/content/guides/ai/vector-indexes.mdx
+++ b/apps/docs/content/guides/ai/vector-indexes.mdx
@@ -34,7 +34,7 @@ For pgvector versions 0.7.0 and above, it's possible to create indexes on vector
You can check your current pgvector version by running: `SELECT * FROM pg_extension WHERE extname = 'vector';` or by navigating to the [Extensions](/dashboard/project/_/database/extensions) tab in your Supabase project dashboard.
-If you are on an earlier version of pgvector, you should [upgrade your project here](/dashboard/project/_/settings/infrastructure).
+If you are on an earlier version of pgvector, you should [upgrade your project here](/dashboard/project/_/settings/general).
## Resources
diff --git a/apps/docs/content/guides/ai/vector-indexes/hnsw-indexes.mdx b/apps/docs/content/guides/ai/vector-indexes/hnsw-indexes.mdx
index 38d06d2bb64..fb77fe5ffd8 100644
--- a/apps/docs/content/guides/ai/vector-indexes/hnsw-indexes.mdx
+++ b/apps/docs/content/guides/ai/vector-indexes/hnsw-indexes.mdx
@@ -45,7 +45,7 @@ For pgvector versions 0.7.0 and above, it's possible to create indexes on vector
You can check your current pgvector version by running: `SELECT * FROM pg_extension WHERE extname = 'vector';` or by navigating to the [Extensions](/dashboard/project/_/database/extensions) tab in your Supabase project dashboard.
-If you are on an earlier version of pgvector, you should [upgrade your project here](/dashboard/project/_/settings/infrastructure).
+If you are on an earlier version of pgvector, you should [upgrade your project here](/dashboard/project/_/settings/general).
## Example with high-dimensional vectors
diff --git a/apps/docs/content/guides/api/rest/postgrest-error-codes.mdx b/apps/docs/content/guides/api/rest/postgrest-error-codes.mdx
index a4a8897deba..4e0d3274518 100644
--- a/apps/docs/content/guides/api/rest/postgrest-error-codes.mdx
+++ b/apps/docs/content/guides/api/rest/postgrest-error-codes.mdx
@@ -195,7 +195,7 @@ limit 100;
-PostgREST error codes are only captured in the logs for projects running V14+. You can check your PostgREST version and upgrade your project in the [Infrastructure Settings](/dashboard/project/_/settings/infrastructure)
+PostgREST error codes are only captured in the logs for projects running V14+. You can check your PostgREST version and upgrade your project in the [General Settings](/dashboard/project/_/settings/general)
diff --git a/apps/docs/content/guides/api/securing-your-api.mdx b/apps/docs/content/guides/api/securing-your-api.mdx
index cf844f70811..5df2faf3cf8 100644
--- a/apps/docs/content/guides/api/securing-your-api.mdx
+++ b/apps/docs/content/guides/api/securing-your-api.mdx
@@ -130,7 +130,7 @@ X-Powered-By: Nerd Rage
Use JSON functions and operators to build dynamic responses from exceptions. Include the `status_text` key in the `detail` clause when you use a custom HTTP status code such as 419. See [JSON Functions and Operators](https://www.postgresql.org/docs/current/functions-json.html) in the Postgres documentation.
-For PostgREST 11 or earlier, use the legacy syntax for raising errors. [Check your PostgREST version](/dashboard/project/_/settings/infrastructure) in the Dashboard. See [Raise errors with HTTP status codes](https://postgrest.org/en/stable/references/errors.html#raise-errors-with-http-status-codes) in the PostgREST documentation.
+For PostgREST 11 or earlier, use the legacy syntax for raising errors. [Check your PostgREST version](/dashboard/project/_/settings/general) in the Dashboard. See [Raise errors with HTTP status codes](https://postgrest.org/en/stable/references/errors.html#raise-errors-with-http-status-codes) in the PostgREST documentation.
## Configure Data API security
diff --git a/apps/docs/content/guides/database/extensions.mdx b/apps/docs/content/guides/database/extensions.mdx
index a9ed68e1739..f83a7af2be2 100644
--- a/apps/docs/content/guides/database/extensions.mdx
+++ b/apps/docs/content/guides/database/extensions.mdx
@@ -56,7 +56,7 @@ In addition to the pre-configured extensions, you can also install your own SQL
## Upgrade extensions
-If a new version of an extension becomes available on Supabase, you need to initiate a software upgrade in the [Infrastructure Settings](/dashboard/project/_/settings/infrastructure) to access it. Software upgrades can also be initiated by restarting your server in the [General Settings](/dashboard/project/_/settings/general).
+If a new version of an extension becomes available on Supabase, you need to initiate a software upgrade in the [General Settings](/dashboard/project/_/settings/general) to access it. Software upgrades can also be initiated by restarting your server in the same [General Settings](/dashboard/project/_/settings/general) page.
## Full list of extensions
diff --git a/apps/docs/content/guides/database/extensions/pg_net.mdx b/apps/docs/content/guides/database/extensions/pg_net.mdx
index bb505ceae20..7d0a3a399c9 100644
--- a/apps/docs/content/guides/database/extensions/pg_net.mdx
+++ b/apps/docs/content/guides/database/extensions/pg_net.mdx
@@ -311,7 +311,7 @@ order by "created" desc;
-Supabase supports reconfiguring pg*net starting from v0.12.0+. For the latest release, initiate a Postgres upgrade in the [Infrastructure Settings](/dashboard/project/*/settings/infrastructure).
+Supabase supports reconfiguring `pg_net` starting from v0.12.0+. For the latest release, initiate a Postgres upgrade in the [General Settings](/dashboard/project/_/settings/general).
diff --git a/apps/docs/content/guides/getting-started/features.mdx b/apps/docs/content/guides/getting-started/features.mdx
index 2fd7bbbfe5e..b573c41d5d1 100644
--- a/apps/docs/content/guides/getting-started/features.mdx
+++ b/apps/docs/content/guides/getting-started/features.mdx
@@ -68,7 +68,7 @@ Deploy read-only databases across multiple regions, for lower latency and better
### Log drains
-Export Supabase logs to third-party providers and external tooling. [Docs](/docs/guides/telemetry/log-drains).
+Export Supabase logs to third-party providers and external tooling. [Docs](/docs/guides/monitoring-and-debugging/log-drains).
## Studio
diff --git a/apps/docs/content/guides/monitoring-and-debugging/metrics/grafana-self-hosted.mdx b/apps/docs/content/guides/monitoring-and-debugging/metrics/grafana-self-hosted.mdx
index dcb7d38db30..ad4ec6fc6b6 100644
--- a/apps/docs/content/guides/monitoring-and-debugging/metrics/grafana-self-hosted.mdx
+++ b/apps/docs/content/guides/monitoring-and-debugging/metrics/grafana-self-hosted.mdx
@@ -10,7 +10,7 @@ Self-hosting [Prometheus](https://prometheus.io/docs/prometheus/latest/installat
Use this guide only if you need full manual control (custom scrape topology, self-hosted Prometheus or non-standard auth).
-Otherwise, use the [Grafana Cloud integration](/docs/guides/telemetry/metrics/grafana-cloud#installation) available in the Supabase Dashboard.
+Otherwise, use the [Grafana Cloud integration](/docs/guides/monitoring-and-debugging/metrics/grafana-cloud#installation) available in the Supabase Dashboard.
diff --git a/apps/docs/content/guides/platform/billing-faq.mdx b/apps/docs/content/guides/platform/billing-faq.mdx
index 4ea5fdb68c7..30c52f06d4e 100644
--- a/apps/docs/content/guides/platform/billing-faq.mdx
+++ b/apps/docs/content/guides/platform/billing-faq.mdx
@@ -12,7 +12,7 @@ subtitle: 'This documentation covers frequently asked questions around subscript
### What are organizations and projects?
The Supabase Platform has "organizations" and "projects". An organization may contain multiple projects. Each project is a dedicated Supabase instance with all of its sub-services including Storage, Auth, Functions and Realtime.
-Each organization only has a single subscription with a single plan (Free, Pro, Team or Enterprise). Project add-ons such as [Compute](/docs/guides/platform/compute-and-disk), [IPv4](/docs/guides/platform/ipv4-address), [Log Drains](/docs/guides/telemetry/log-drains), [Advanced MFA](/docs/guides/auth/auth-mfa/phone), [Custom Domains](/docs/guides/platform/custom-domains) and [PITR](/docs/guides/platform/backups#point-in-time-recovery) are configured per project and are added to your organization subscription.
+Each organization only has a single subscription with a single plan (Free, Pro, Team or Enterprise). Project add-ons such as [Compute](/docs/guides/platform/compute-and-disk), [IPv4](/docs/guides/platform/ipv4-address), [Log Drains](/docs/guides/monitoring-and-debugging/log-drains), [Advanced MFA](/docs/guides/auth/auth-mfa/phone), [Custom Domains](/docs/guides/platform/custom-domains) and [PITR](/docs/guides/platform/backups#point-in-time-recovery) are configured per project and are added to your organization subscription.
Read more on [About billing on Supabase](/docs/guides/platform/billing-on-supabase#organization-based-billing).
diff --git a/apps/docs/content/guides/platform/network-restrictions.mdx b/apps/docs/content/guides/platform/network-restrictions.mdx
index b471ba27eab..1427441a215 100644
--- a/apps/docs/content/guides/platform/network-restrictions.mdx
+++ b/apps/docs/content/guides/platform/network-restrictions.mdx
@@ -8,7 +8,7 @@ This topic explains how to configure network restrictions for your Supabase proj
-If you can't find the Network Restrictions section in your [Database Settings](/dashboard/project/_/database/settings), update your Postgres version in [Infrastructure Settings](/dashboard/project/_/settings/infrastructure).
+If you can't find the Network Restrictions section in your [Database Settings](/dashboard/project/_/database/settings), update your Postgres version in [General Settings](/dashboard/project/_/settings/general).
diff --git a/apps/docs/content/guides/platform/project-transfer.mdx b/apps/docs/content/guides/platform/project-transfer.mdx
index e463bf2aa77..cc4718c6340 100644
--- a/apps/docs/content/guides/platform/project-transfer.mdx
+++ b/apps/docs/content/guides/platform/project-transfer.mdx
@@ -43,7 +43,7 @@ Target organization - the organization you want to move the project to
## Usage-billing and project add-ons
-For usage metrics such as disk size, egress or image transformations and project add-ons such as [Compute Add-On](/docs/guides/platform/compute-and-disk), [Point-In-Time-Recovery](/docs/guides/platform/backups#point-in-time-recovery), [IPv4](/docs/guides/platform/ipv4-address), [Log Drains](/docs/guides/telemetry/log-drains), [Advanced MFA](/docs/guides/auth/auth-mfa/phone) or a [Custom Domain](/docs/guides/platform/custom-domains), the source organization will still be charged for the usage up until the transfer. The charges will be added to the invoice when the billing cycle resets.
+For usage metrics such as disk size, egress or image transformations and project add-ons such as [Compute Add-On](/docs/guides/platform/compute-and-disk), [Point-In-Time-Recovery](/docs/guides/platform/backups#point-in-time-recovery), [IPv4](/docs/guides/platform/ipv4-address), [Log Drains](/docs/guides/monitoring-and-debugging/log-drains), [Advanced MFA](/docs/guides/auth/auth-mfa/phone) or a [Custom Domain](/docs/guides/platform/custom-domains), the source organization will still be charged for the usage up until the transfer. The charges will be added to the invoice when the billing cycle resets.
The target organization will be charged at the end of the billing cycle for usage after the project transfer.
diff --git a/apps/docs/content/guides/platform/temporary-access.mdx b/apps/docs/content/guides/platform/temporary-access.mdx
index e9cadf3a61f..2862e3bdcba 100644
--- a/apps/docs/content/guides/platform/temporary-access.mdx
+++ b/apps/docs/content/guides/platform/temporary-access.mdx
@@ -9,7 +9,7 @@ Enabling temporary access only applies to connections to Postgres and Supavisor
-Projects need to be at least on Postgres 17.6.1.081 (or higher) to enable temporary access. You can find the Postgres version of your project on the [infrastructure settings](/dashboard/project/_/settings/infrastructure) page. If your project is on an older version, you will need to [upgrade](/docs/guides/platform/upgrading) to use this feature.
+Projects need to be at least on Postgres 17.6.1.081 (or higher) to enable temporary access. You can find the Postgres version of your project on the [General Settings](/dashboard/project/_/settings/general) page. If your project is on an older version, you will need to [upgrade](/docs/guides/platform/upgrading) to use this feature.
diff --git a/apps/docs/content/guides/platform/upgrading.mdx b/apps/docs/content/guides/platform/upgrading.mdx
index beec25a2169..1400a906e59 100644
--- a/apps/docs/content/guides/platform/upgrading.mdx
+++ b/apps/docs/content/guides/platform/upgrading.mdx
@@ -18,7 +18,7 @@ Free projects will move to the latest minor version when their paused project is
The upgrade process is as follows:
-1. Use the "Upgrade project" button on the [Infrastructure](/dashboard/project/_/settings/infrastructure) section of your dashboard.
+1. Use the "Upgrade project" button on the [General settings](/dashboard/project/_/settings/general) page of your dashboard.
2. An estimate of the time to upgrade is shown and anything that needs to be addressed before you are eligible to upgrade is shown as a warning. Ensure you have reviewed the [caveats](#caveats) section of this document before executing the upgrade.
3. Your project is taken offline and the Dashboard shows the upgrade status.
4. Behind the scenes, a new instance is created running the latest version of Supabase.
@@ -39,7 +39,7 @@ When upgrading, a notification will inform you about what is blocking the upgrad
3. Logical replication slots must be dropped.
4. Deprecated/unsupported extensions must be dropped. Extensions can have dependencies, make sure you backup that data to restore it after the upgrade, with the updated extension version.
-Newer versions of services can break functionality or change the performance characteristics you rely on. If your project is eligible for an upgrade, you will be able to find your current service versions from within [the Supabase dashboard](/dashboard/project/_/settings/infrastructure).
+Newer versions of services can break functionality or change the performance characteristics you rely on. If your project is eligible for an upgrade, you will be able to find your current service versions from within [the Supabase dashboard](/dashboard/project/_/settings/general).
Breaking changes are generally only present in major version upgrades of Postgres and PostgREST. You can find their respective release notes at:
diff --git a/apps/docs/content/troubleshooting/forbidden-resource-error-from-the-cli-L6rm6l.mdx b/apps/docs/content/troubleshooting/forbidden-resource-error-from-the-cli-L6rm6l.mdx
index 2c8fba0f00f..5fef06d5586 100644
--- a/apps/docs/content/troubleshooting/forbidden-resource-error-from-the-cli-L6rm6l.mdx
+++ b/apps/docs/content/troubleshooting/forbidden-resource-error-from-the-cli-L6rm6l.mdx
@@ -18,7 +18,7 @@ This error typically occurs as a protective measure to prevent unauthorized acce
To address this issue, we recommend following these troubleshooting steps:
-- Verify Project ID: Ensure the $PROJECT*REF variable in your commands contains the correct Project ID. You can find your Reference ID under [Project -> Settings -> General](/dashboard/project/*/settings/general) in your Supabase Dashboard. A Reference ID looks something like `xvljpkujuwroxcuvossw`.
+- Verify Project ID: Ensure the `$PROJECT_REF` variable in your commands contains the correct Project ID. You can find your Reference ID under [Project -> Settings -> General](/dashboard/project/_/settings/general) in your Supabase Dashboard. A Reference ID looks something like `xvljpkujuwroxcuvossw`.
- Authorization Check: Confirm that you’ve been properly authorized. You can also generate a new Access Token in your dashboard and use it for login. Generate a new token [here](/dashboard/account/tokens) and use it to [log in](/docs/reference/cli/supabase-login).
- Re-link Project: Try [re-linking](/docs/reference/cli/supabase-link) your project with the newly generated token.
- Owner/Admin Permissions: Make sure you have [Owner/Admin](/docs/guides/platform/access-control) permissions for the project.
diff --git a/apps/docs/content/troubleshooting/grafana-not-displaying-data-sXJrMj.mdx b/apps/docs/content/troubleshooting/grafana-not-displaying-data-sXJrMj.mdx
index b9caf4f6c0f..c13e0e40dd2 100644
--- a/apps/docs/content/troubleshooting/grafana-not-displaying-data-sXJrMj.mdx
+++ b/apps/docs/content/troubleshooting/grafana-not-displaying-data-sXJrMj.mdx
@@ -7,7 +7,7 @@ keywords = [ "grafana", "docker", "metrics", "configuration" ]
database_id = "76a4099e-450f-4b5b-a539-224760348c18"
---
-This guide is for identifying configuration mistakes in [self-hosted Supabase Grafana installations](/docs/guides/telemetry/metrics/grafana-self-hosted)
+This guide is for identifying configuration mistakes in [self-hosted Supabase Grafana installations](/docs/guides/monitoring-and-debugging/metrics/grafana-self-hosted)
## Step 1: Ping your Grafana endpoint
diff --git a/apps/docs/content/troubleshooting/increase-vector-lookup-speeds-by-applying-an-hsnw-index-ohLHUM.mdx b/apps/docs/content/troubleshooting/increase-vector-lookup-speeds-by-applying-an-hsnw-index-ohLHUM.mdx
index 93124060089..53fd669bd82 100644
--- a/apps/docs/content/troubleshooting/increase-vector-lookup-speeds-by-applying-an-hsnw-index-ohLHUM.mdx
+++ b/apps/docs/content/troubleshooting/increase-vector-lookup-speeds-by-applying-an-hsnw-index-ohLHUM.mdx
@@ -32,7 +32,7 @@ Applying an index can be slow and computationally expensive, so there are a few
**1. Make sure your pgvector is the latest available version on Supabase.**
-Versions 0.6 and later have accelerated HNSW build speeds. You can observe your current version in the [Dashboard's Extensions Page](/dashboard/project/_/database/extensions). You can perform a software upgrade in the [Infrastructure Settings ](/dashboard/project/_/settings/infrastructure)if necessary.
+Versions 0.6 and later have accelerated HNSW build speeds. You can observe your current version in the [Dashboard's Extensions Page](/dashboard/project/_/database/extensions). You can perform a software upgrade in the [General Settings](/dashboard/project/_/settings/general) if necessary.
**2. Setting up an external connection**
diff --git a/apps/docs/content/troubleshooting/interpreting-supabase-grafana-cpu-charts-9JSlkC.mdx b/apps/docs/content/troubleshooting/interpreting-supabase-grafana-cpu-charts-9JSlkC.mdx
index a5828b5c873..5e86d52777e 100644
--- a/apps/docs/content/troubleshooting/interpreting-supabase-grafana-cpu-charts-9JSlkC.mdx
+++ b/apps/docs/content/troubleshooting/interpreting-supabase-grafana-cpu-charts-9JSlkC.mdx
@@ -7,7 +7,7 @@ keywords = [ "cpu", "grafana", "metrics" ]
database_id = "ef05da0a-f8bc-44a4-9719-5ae811dba104"
---
-> [Guide](/docs/guides/telemetry/metrics/grafana-self-hosted) for setting up Supabase Grafana
+> [Guide](/docs/guides/monitoring-and-debugging/metrics/grafana-self-hosted) for setting up Supabase Grafana
## CPU
diff --git a/apps/docs/content/troubleshooting/pgcron-debugging-guide-n1KTaz.mdx b/apps/docs/content/troubleshooting/pgcron-debugging-guide-n1KTaz.mdx
index 9223be77fd3..7602ce6a064 100644
--- a/apps/docs/content/troubleshooting/pgcron-debugging-guide-n1KTaz.mdx
+++ b/apps/docs/content/troubleshooting/pgcron-debugging-guide-n1KTaz.mdx
@@ -25,7 +25,7 @@ If you are trying to make changes, use the cron functions. If the cron functions
## Cron Jobs are not running
-> You should consider initiating a software upgrade in the [Infrastructure Settings](/dashboard/project/_/settings/infrastructure) if your Postgres version is below v15.6.1.122. Upgrading will give you access to pg_cron v1.6.4+, which has many bug fixes and auto-revive capabilities.
+> You should consider initiating a software upgrade in the [General Settings](/dashboard/project/_/settings/general) if your Postgres version is below v15.6.1.122. Upgrading will give you access to pg_cron v1.6.4+, which has many bug fixes and auto-revive capabilities.
### Debugging steps:
@@ -114,7 +114,7 @@ You can view your concurrent peak connection usage throughout the day at the bot
Unfortunately, excessive resource strain can slow down or disrupt jobs.
-Go to the [reports page](/dashboard/project/_/observability/database) (or [Supabase Grafana](/docs/guides/telemetry/metrics/grafana-self-hosted) if you have it setup), and check for signs of resource exhaustion. If it's clear your database is under pressure, consider upgrading your compute add-on or following the advice from one of the optimization guides:
+Go to the [reports page](/dashboard/project/_/observability/database) (or [Supabase Grafana](/docs/guides/monitoring-and-debugging/metrics/grafana-self-hosted) if you have it setup), and check for signs of resource exhaustion. If it's clear your database is under pressure, consider upgrading your compute add-on or following the advice from one of the optimization guides:
- [Connections](https://github.com/orgs/supabase/discussions/27141)
- [Disk/IO](https://github.com/orgs/supabase/discussions/27003)
@@ -127,7 +127,7 @@ It is important to make sure you are running the latest release of pg_cron (1.6.
#### Check the log explorer for more information
-Although pg*cron records errors in the `cron.job_run_details` table, in rare cases, more information can be found in the general Postgres logs. You can check the [Log Explorer](/dashboard/project/*/logs/explorer) for failure events with the following query
+Although `pg_cron` records errors in the `cron.job_run_details` table, in rare cases, more information can be found in the general Postgres logs. You can check the [Log Explorer](/dashboard/project/_/logs/explorer) for failure events with the following query
```sql
select
@@ -152,7 +152,7 @@ order by timestamp desc
limit 100;
```
-If you're interested in modifying the query, there is an advanced [guide](https://github.com/orgs/supabase/discussions/26224) for navigating the Postgres logs and a general purpose [one](/docs/guides/telemetry/advanced-log-filtering) for applying filters.
+If you're interested in modifying the query, there is an advanced [guide](https://github.com/orgs/supabase/discussions/26224) for navigating the Postgres logs and a general-purpose [one](/docs/guides/monitoring-and-debugging/advanced-log-filtering) for applying filters.
@@ -190,7 +190,7 @@ You can then search for your custom messages in the [Logs Interface](/dashboard/
#### Upgrading pg_cron version
-The current version of pg*cron on Supabase is 1.6.4. It comes with a [few bug fixes](https://github.com/citusdata/pg_cron/releases/tag/v1.6.4). You should consider upgrading to Postgres v15.6.1.122+ in the[ Infrastructure Settings](/dashboard/project/*/settings/infrastructure) to get the latest extension.
+The current version of `pg_cron` on Supabase is 1.6.4. It comes with a [few bug fixes](https://github.com/citusdata/pg_cron/releases/tag/v1.6.4). You should consider upgrading to Postgres v15.6.1.122+ in the [General Settings](/dashboard/project/_/settings/general) to get the latest extension.
diff --git a/apps/docs/content/troubleshooting/postgrest-error-400-column-example_tableexample_column-does-not-exist-when-using-or-operators-46ff23.mdx b/apps/docs/content/troubleshooting/postgrest-error-400-column-example_tableexample_column-does-not-exist-when-using-or-operators-46ff23.mdx
index e132244871a..aac2981217f 100644
--- a/apps/docs/content/troubleshooting/postgrest-error-400-column-example_tableexample_column-does-not-exist-when-using-or-operators-46ff23.mdx
+++ b/apps/docs/content/troubleshooting/postgrest-error-400-column-example_tableexample_column-does-not-exist-when-using-or-operators-46ff23.mdx
@@ -17,14 +17,14 @@ The bug is triggered when an `or()` filter is included in a mutation request. Po
## How to confirm
1. **Reproduce the asymmetry** — run the same filter as a `GET` request. If it succeeds but the `PATCH`/`POST`/`DELETE` fails with the same column reference, the bug is the likely cause.
-2. **Check your PostgREST version** — go to [Project Settings > Infrastructure](/dashboard/project/_/settings/infrastructure) and note the Postgres version. PostgREST 14.1 and earlier are affected; 14.4+ includes the fix.
+2. **Check your PostgREST version** — go to [Project Settings > General](/dashboard/project/_/settings/general) and note the Postgres version. PostgREST 14.1 and earlier are affected; 14.4+ includes the fix.
3. **Check Postgres logs** — if you have logging enabled, you should see `column "example_column" does not exist` errors correlating with the timestamps of the failed mutation requests.
## Resolution
### Option 1: Upgrade (permanent fix)
-Navigate to [Project Settings > Infrastructure](/dashboard/project/_/settings/infrastructure) and upgrade to the latest Postgres version. This automatically upgrades PostgREST to 14.5+, where the bug is resolved.
+Navigate to [Project Settings > General](/dashboard/project/_/settings/general) and upgrade to the latest Postgres version. This automatically upgrades PostgREST to 14.5+, where the bug is resolved.
### Option 2: Query workaround (immediate)
diff --git a/apps/docs/content/troubleshooting/rls-performance-and-best-practices-Z5Jjwv.mdx b/apps/docs/content/troubleshooting/rls-performance-and-best-practices-Z5Jjwv.mdx
index 00af4c77436..7717cc606e8 100644
--- a/apps/docs/content/troubleshooting/rls-performance-and-best-practices-Z5Jjwv.mdx
+++ b/apps/docs/content/troubleshooting/rls-performance-and-best-practices-Z5Jjwv.mdx
@@ -123,7 +123,7 @@ Show RLS and before after for above examples.
| ---- | --------------------------------- | -------------------------------------------------- | ------- | ------ |
| 1 | auth.uid()=user_id | user_id indexed | 171ms | <.1 |
| 2a | auth.uid()=user_id | (select auth.uid()) = user_id | 179 | 9 |
-| 2b | is*admin() \_table join* | (select is*admin()) \_table join* | 11,000 | 7 |
+| 2b | `is_admin()` _table join_ | (select `is_admin()`) _table join_ | 11,000 | 7 |
| 2c | is_admin() OR auth.uid()=user_id | (select is_admin()) OR (select auth.uid()=user_id) | 11,000 | 10 |
| 2d | has_role()=role | (select has_role())=role | 178,000 | 12 |
| 2e | team_id=any(user_teams()) | team_id=any(array(select user_teams())) | 173000 | 16 |
diff --git a/apps/docs/content/troubleshooting/webhook-debugging-guide-M8sk47.mdx b/apps/docs/content/troubleshooting/webhook-debugging-guide-M8sk47.mdx
index bf32e5ee9b0..c871926220c 100644
--- a/apps/docs/content/troubleshooting/webhook-debugging-guide-M8sk47.mdx
+++ b/apps/docs/content/troubleshooting/webhook-debugging-guide-M8sk47.mdx
@@ -7,7 +7,7 @@ keywords = [ "webhook", "timeout", "pg_net", "postgres", "trigger" ]
database_id = "a5524182-9dc4-4470-86fe-45ace109a53a"
---
-> NOTE: version 0.10.0 of pg*net is out. You should consider updating your database in the[ Infrastructure Settings](/dashboard/project/*/settings/infrastructure) if you are on a prior version. If you do not know your version, you can check the [Extensions Dashboard](/dashboard/project/_/database/extensions).
+> NOTE: version 0.10.0 of `pg_net` is out. You should consider updating your database in the [General Settings](/dashboard/project/_/settings/general) if you are on a prior version. If you do not know your version, you can check the [Extensions Dashboard](/dashboard/project/_/database/extensions).
**Debugging Steps**
@@ -34,7 +34,7 @@ The `net` tables are special and if triggers on them fail or call a pg_net funct
**3. Check for timeout errors**
-> **NOTE**: The timeout issue has been patched in pg*net v0.11. It is available in Postgres 15.6.1.135 and above. You can upgrade your version of Postgres in the [Infrastructure Settings.](/dashboard/project/*/settings/infrastructure)
+> **NOTE**: The timeout issue has been patched in `pg_net` v0.11. It is available in Postgres 15.6.1.135 and above. You can upgrade your version of Postgres in the [General Settings](/dashboard/project/_/settings/general).
Go to your [Table Editor](/dashboard/project/_/editor/) and navigate to the net schema. It will contain two tables: