Skip to content

The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications.

Changed order that CLI flags are applied in (#47098)

TheOtherBrian1bd18ff98e9fe
diff --git a/apps/docs/content/guides/database/custom-postgres-config.mdx b/apps/docs/content/guides/database/custom-postgres-config.mdx
index 51c533bf808..efb45d922de 100644
--- a/apps/docs/content/guides/database/custom-postgres-config.mdx
+++ b/apps/docs/content/guides/database/custom-postgres-config.mdx
@@ -160,25 +160,25 @@ To update Postgres configurations, use the [`postgres config`](/docs/reference/c
```bash
supabase --experimental \
---project-ref <project-ref> \
-postgres-config update --config shared_buffers=250MB
+postgres-config update --config shared_buffers=250MB \
+--project-ref <project-ref>
```
By default, the CLI will merge any provided config overrides with any existing ones. The `--replace-existing-overrides` flag can be used to instead force all existing overrides to be replaced with the ones being provided:
```bash
supabase --experimental \
---project-ref <project-ref> \
postgres-config update --config max_parallel_workers=3 \
---replace-existing-overrides
+--replace-existing-overrides \
+--project-ref <project-ref>
```
To delete specific configuration overrides, use the `postgres-config delete` command:
```bash
supabase --experimental \
---project-ref <project-ref> \
-postgres-config delete --config shared_buffers,work_mem
+postgres-config delete --config shared_buffers,work_mem \
+--project-ref <project-ref>
```
By default, CLI v2 (≥ 2.0.0) checks the parameter’s context and requests the correct action (reload or restart):