diff --git a/apps/docs/content/guides/platform/custom-postgres-config.mdx b/apps/docs/content/guides/platform/custom-postgres-config.mdx
index 069cb841593..cfa63cf2daf 100644
--- a/apps/docs/content/guides/platform/custom-postgres-config.mdx
+++ b/apps/docs/content/guides/platform/custom-postgres-config.mdx
@@ -32,7 +32,6 @@ The following parameters are available for overrides:
 1. [max_worker_processes](https://postgresqlco.nf/doc/en/param/max_worker_processes/)
 1. [session_replication_role](https://postgresqlco.nf/doc/en/param/session_replication_role/)
 1. [shared_buffers](https://postgresqlco.nf/doc/en/param/shared_buffers/)
-1. [statement_timeout](https://postgresqlco.nf/doc/en/param/statement_timeout/)
 1. [work_mem](https://postgresqlco.nf/doc/en/param/work_mem/)
 
 ### Setting config using the CLI
@@ -64,17 +63,6 @@ max_parallel_workers    |3        |
 - End of Custom Postgres Config -
 ```
 
-When configuring parameters that require time units, such as `statement_timeout`, the CLI expects a string value with a time unit. Supported units include `ms`, `s`, and `min`.
-
-```bash
-$ supabase --experimental --project-ref <project-ref> postgres-config update --config statement_timeout=1000ms
-
-- Custom Postgres Config -
-Config            |Value   |
-statement_timeout |1000ms  |
-- End of Custom Postgres Config -
-```
-
 ## Considerations
 
 1. The Postgres cluster will be restarted in order to change the configuration being used. This will cause momentary disruption to existing database connections; in most cases this should not take more than a few seconds.