From 494b170b2a92a73a32986164dde4e7bc4ad0df58 Mon Sep 17 00:00:00 2001 From: Claude Date: Mon, 20 Jul 2026 20:17:41 +0000 Subject: [PATCH 1/3] docs: document three system parameters on ALTER SYSTEM SET page Add persist_pg_consensus_read_committed, pg_source_validate_timeline, and sql_server_source_validate_restore_history to the "Key configuration parameters" table on the ALTER SYSTEM SET page. These parameters were previously undocumented. Descriptions are grounded in the flag definitions in src/persist/src/postgres.rs and src/storage-types/src/dyncfgs.rs. --- doc/user/content/headless/configuration-parameters.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/doc/user/content/headless/configuration-parameters.md b/doc/user/content/headless/configuration-parameters.md index 7859a102f98fd..eeb4e72f231bb 100644 --- a/doc/user/content/headless/configuration-parameters.md +++ b/doc/user/content/headless/configuration-parameters.md @@ -8,7 +8,10 @@ Name | Default value | Descr `cluster` | `quickstart` | The current cluster. | Yes `cluster_replica` | | The target cluster replica for `SELECT` queries. | Yes `database` | `materialize` | The current database. | Yes +`persist_pg_consensus_read_committed` | `false` | Boolean flag indicating whether to run persist consensus connections under `READ COMMITTED` isolation instead of `SERIALIZABLE` when using a PostgreSQL backend. Must be disabled when using a CockroachDB backend. | [Contact support] +`pg_source_validate_timeline` | `true` | Boolean flag indicating whether to treat an upstream timeline switch on a [PostgreSQL source](/sql/create-source/postgres/) as a definite error that forces the source to be recreated. Disable only for highly available upstream databases that guarantee failover without data loss (for example, Cloud SQL or AlloyDB); disabling it makes you responsible for recreating the source if a timeline change introduces data loss. | [Contact support] `search_path` | `public` | The schema search order for names that are not schema-qualified. | Yes +`sql_server_source_validate_restore_history` | `true` | Boolean flag indicating whether to treat an upstream restore-history change on a [SQL Server source](/sql/create-source/sql-server/) as a definite error that forces the source to be recreated. Disable only for highly available upstream databases that guarantee continuity without data loss (for example, Always On availability groups); disabling it makes you responsible for recreating the source if a change introduces data loss. | [Contact support] `transaction_isolation` | `strict serializable` | The transaction isolation level. For more information, see [Isolation level](/reference/isolation-level/).

Accepts values: `serializable`, `strict serializable`{{< if-released "v26.29" >}}, `bounded staleness ` (for example, `bounded staleness 5s`){{< /if-released >}}. | Yes ### Other configuration parameters From 3db55b7b6ae52e55bf1ca0ddef42be9b1ef4ae4e Mon Sep 17 00:00:00 2001 From: Claude Date: Mon, 20 Jul 2026 20:21:09 +0000 Subject: [PATCH 2/3] docs: replace semicolons with periods in two system param descriptions --- doc/user/content/headless/configuration-parameters.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/user/content/headless/configuration-parameters.md b/doc/user/content/headless/configuration-parameters.md index eeb4e72f231bb..924edd31cc799 100644 --- a/doc/user/content/headless/configuration-parameters.md +++ b/doc/user/content/headless/configuration-parameters.md @@ -9,9 +9,9 @@ Name | Default value | Descr `cluster_replica` | | The target cluster replica for `SELECT` queries. | Yes `database` | `materialize` | The current database. | Yes `persist_pg_consensus_read_committed` | `false` | Boolean flag indicating whether to run persist consensus connections under `READ COMMITTED` isolation instead of `SERIALIZABLE` when using a PostgreSQL backend. Must be disabled when using a CockroachDB backend. | [Contact support] -`pg_source_validate_timeline` | `true` | Boolean flag indicating whether to treat an upstream timeline switch on a [PostgreSQL source](/sql/create-source/postgres/) as a definite error that forces the source to be recreated. Disable only for highly available upstream databases that guarantee failover without data loss (for example, Cloud SQL or AlloyDB); disabling it makes you responsible for recreating the source if a timeline change introduces data loss. | [Contact support] +`pg_source_validate_timeline` | `true` | Boolean flag indicating whether to treat an upstream timeline switch on a [PostgreSQL source](/sql/create-source/postgres/) as a definite error that forces the source to be recreated. Disable only for highly available upstream databases that guarantee failover without data loss (for example, Cloud SQL or AlloyDB). Disabling it makes you responsible for recreating the source if a timeline change introduces data loss. | [Contact support] `search_path` | `public` | The schema search order for names that are not schema-qualified. | Yes -`sql_server_source_validate_restore_history` | `true` | Boolean flag indicating whether to treat an upstream restore-history change on a [SQL Server source](/sql/create-source/sql-server/) as a definite error that forces the source to be recreated. Disable only for highly available upstream databases that guarantee continuity without data loss (for example, Always On availability groups); disabling it makes you responsible for recreating the source if a change introduces data loss. | [Contact support] +`sql_server_source_validate_restore_history` | `true` | Boolean flag indicating whether to treat an upstream restore-history change on a [SQL Server source](/sql/create-source/sql-server/) as a definite error that forces the source to be recreated. Disable only for highly available upstream databases that guarantee continuity without data loss (for example, Always On availability groups). Disabling it makes you responsible for recreating the source if a change introduces data loss. | [Contact support] `transaction_isolation` | `strict serializable` | The transaction isolation level. For more information, see [Isolation level](/reference/isolation-level/).

Accepts values: `serializable`, `strict serializable`{{< if-released "v26.29" >}}, `bounded staleness ` (for example, `bounded staleness 5s`){{< /if-released >}}. | Yes ### Other configuration parameters From fafdd145ca6180f60d9b61889c3fc0664e815121 Mon Sep 17 00:00:00 2001 From: Claude Date: Mon, 20 Jul 2026 21:25:58 +0000 Subject: [PATCH 3/3] docs: move source-validation flags to Other config parameters table --- doc/user/content/headless/configuration-parameters.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/user/content/headless/configuration-parameters.md b/doc/user/content/headless/configuration-parameters.md index 924edd31cc799..83d087a41c711 100644 --- a/doc/user/content/headless/configuration-parameters.md +++ b/doc/user/content/headless/configuration-parameters.md @@ -8,10 +8,7 @@ Name | Default value | Descr `cluster` | `quickstart` | The current cluster. | Yes `cluster_replica` | | The target cluster replica for `SELECT` queries. | Yes `database` | `materialize` | The current database. | Yes -`persist_pg_consensus_read_committed` | `false` | Boolean flag indicating whether to run persist consensus connections under `READ COMMITTED` isolation instead of `SERIALIZABLE` when using a PostgreSQL backend. Must be disabled when using a CockroachDB backend. | [Contact support] -`pg_source_validate_timeline` | `true` | Boolean flag indicating whether to treat an upstream timeline switch on a [PostgreSQL source](/sql/create-source/postgres/) as a definite error that forces the source to be recreated. Disable only for highly available upstream databases that guarantee failover without data loss (for example, Cloud SQL or AlloyDB). Disabling it makes you responsible for recreating the source if a timeline change introduces data loss. | [Contact support] `search_path` | `public` | The schema search order for names that are not schema-qualified. | Yes -`sql_server_source_validate_restore_history` | `true` | Boolean flag indicating whether to treat an upstream restore-history change on a [SQL Server source](/sql/create-source/sql-server/) as a definite error that forces the source to be recreated. Disable only for highly available upstream databases that guarantee continuity without data loss (for example, Always On availability groups). Disabling it makes you responsible for recreating the source if a change introduces data loss. | [Contact support] `transaction_isolation` | `strict serializable` | The transaction isolation level. For more information, see [Isolation level](/reference/isolation-level/).

Accepts values: `serializable`, `strict serializable`{{< if-released "v26.29" >}}, `bounded staleness ` (for example, `bounded staleness 5s`){{< /if-released >}}. | Yes ### Other configuration parameters @@ -59,11 +56,14 @@ Name | Default value | Descr `min_timestamp_interval` | `1s` | The lower bound for the `TIMESTAMP INTERVAL` option of [`CREATE SOURCE`](/sql/create-source/) and [`ALTER SOURCE`](/sql/alter-source/). Statements that request a timestamp interval smaller than this value are rejected. Accepts positive [interval](/sql/types/interval/) values (e.g. `'500ms'`, `'1s'`). | [Contact support] `mz_version` | Version-dependent | Shows the Materialize server version. | No `network_policy` | `default` | The default network policy for the region. | Yes +`persist_pg_consensus_read_committed` | `false` | Boolean flag indicating whether to run persist consensus connections under `READ COMMITTED` isolation instead of `SERIALIZABLE` when using a PostgreSQL backend. Must be disabled when using a CockroachDB backend. | [Contact support] +`pg_source_validate_timeline` | `true` | Boolean flag indicating whether to treat an upstream timeline switch on a [PostgreSQL source](/sql/create-source/postgres/) as a definite error that forces the source to be recreated. Disable only for highly available upstream databases that guarantee failover without data loss (for example, Cloud SQL or AlloyDB). Disabling it makes you responsible for recreating the source if a timeline change introduces data loss. | [Contact support] `real_time_recency` | `false` | Boolean flag indicating whether [real-time recency](/reference/isolation-level/#real-time-recency) is enabled for the current session. | [Contact support] `real_time_recency_timeout` | `10s` | Sets the maximum allowed duration of `SELECT` statements that actively use [real-time recency](/reference/isolation-level/#real-time-recency). If this value is specified without units, it is taken as milliseconds (`ms`). | Yes `server_version_num` | Version-dependent | The PostgreSQL compatible server version as an integer. | No `server_version` | Version-dependent | The PostgreSQL compatible server version. | No `sql_safe_updates` | `false` | Boolean flag indicating whether to prohibit SQL statements that may be overly destructive. | Yes +`sql_server_source_validate_restore_history` | `true` | Boolean flag indicating whether to treat an upstream restore-history change on a [SQL Server source](/sql/create-source/sql-server/) as a definite error that forces the source to be recreated. Disable only for highly available upstream databases that guarantee continuity without data loss (for example, Always On availability groups). Disabling it makes you responsible for recreating the source if a change introduces data loss. | [Contact support] `standard_conforming_strings` | `true` | Boolean flag indicating whether ordinary string literals (`'...'`) should treat backslashes literally. The only supported value is `true`. | Yes `statement_timeout` | `10s` | The maximum allowed duration of the read portion of write operations; i.e., the `SELECT` portion of `INSERT INTO ... (SELECT ...)`; the `WHERE` portion of `UPDATE ... WHERE ...` and `DELETE FROM ... WHERE ...`. If this value is specified without units, it is taken as milliseconds (`ms`). | Yes `timezone` | `UTC` | The time zone for displaying and interpreting timestamps. The only supported value is `UTC`. | Yes