Skip to content

Commit a084061

Browse files
rmlovelandrmloveland
authored
Secondary regions do not work with RBR tables (#19436)
Fixes DOC-8959 NB. This PR includes backported changes to v23.*, v24.*, and v25.*
1 parent f6df22e commit a084061

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

43 files changed

+181
-7
lines changed

‎src/current/_includes/v23.1/known-limitations/secondary-regions-with-regional-by-row-tables.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
[Secondary regions]({% link {{ page.version.version }}/multiregion-overview.md %}#secondary-regions) are not compatible with databases containing [`REGIONAL BY ROW`]({% link {{ page.version.version }}/table-localities.md %}#regional-by-row-tables) tables. CockroachDB does not prevent you from defining secondary regions on databases with regional by row tables, but the interaction of these features is not supported.
2+
3+
Therefore, Cockroach Labs recommends that you avoid defining secondary regions on databases that use regional by row table configurations.

‎src/current/_includes/v23.1/sql/regional-by-row-table-description.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,4 +12,8 @@ To take advantage of regional by row tables:
1212

1313
For instructions showing how to set a table's locality to `REGIONAL BY ROW` and configure the home regions of its rows, see [`ALTER TABLE ... SET LOCALITY`]({% link {{ page.version.version }}/alter-table.md %}#crdb_region).
1414

15-
For more information on regional by row tables, see the [Cockroach Labs blog post](https://www.cockroachlabs.com/blog/regional-by-row/).
15+
For more information on regional by row tables, see the [Cockroach Labs blog post](https://www.cockroachlabs.com/blog/regional-by-row/).
16+
17+
{{site.data.alerts.callout_danger}}
18+
{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
19+
{{site.data.alerts.end}}

‎src/current/_includes/v23.2/known-limitations/secondary-regions-with-regional-by-row-tables.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
[Secondary regions]({% link {{ page.version.version }}/multiregion-overview.md %}#secondary-regions) are not compatible with databases containing [`REGIONAL BY ROW`]({% link {{ page.version.version }}/table-localities.md %}#regional-by-row-tables) tables. CockroachDB does not prevent you from defining secondary regions on databases with regional by row tables, but the interaction of these features is not supported.
2+
3+
Therefore, Cockroach Labs recommends that you avoid defining secondary regions on databases that use regional by row table configurations.

‎src/current/_includes/v23.2/sql/regional-by-row-table-description.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,4 +12,8 @@ To take advantage of regional by row tables:
1212

1313
For instructions showing how to set a table's locality to `REGIONAL BY ROW` and configure the home regions of its rows, see [`ALTER TABLE ... SET LOCALITY`]({% link {{ page.version.version }}/alter-table.md %}#crdb_region).
1414

15-
For more information on regional by row tables, see the [Cockroach Labs blog post](https://www.cockroachlabs.com/blog/regional-by-row/).
15+
For more information on regional by row tables, see the [Cockroach Labs blog post](https://www.cockroachlabs.com/blog/regional-by-row/).
16+
17+
{{site.data.alerts.callout_danger}}
18+
{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
19+
{{site.data.alerts.end}}

‎src/current/_includes/v24.1/known-limitations/secondary-regions-with-regional-by-row-tables.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
[Secondary regions]({% link {{ page.version.version }}/multiregion-overview.md %}#secondary-regions) are not compatible with databases containing [`REGIONAL BY ROW`]({% link {{ page.version.version }}/table-localities.md %}#regional-by-row-tables) tables. CockroachDB does not prevent you from defining secondary regions on databases with regional by row tables, but the interaction of these features is not supported.
2+
3+
Therefore, Cockroach Labs recommends that you avoid defining secondary regions on databases that use regional by row table configurations.

‎src/current/_includes/v24.1/sql/regional-by-row-table-description.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,4 +12,8 @@ To take advantage of regional by row tables:
1212

1313
For instructions showing how to set a table's locality to `REGIONAL BY ROW` and configure the home regions of its rows, see [`ALTER TABLE ... SET LOCALITY`]({% link {{ page.version.version }}/alter-table.md %}#crdb_region).
1414

15-
For more information on regional by row tables, see the [Cockroach Labs blog post](https://www.cockroachlabs.com/blog/regional-by-row/).
15+
For more information on regional by row tables, see the [Cockroach Labs blog post](https://www.cockroachlabs.com/blog/regional-by-row/).
16+
17+
{{site.data.alerts.callout_danger}}
18+
{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
19+
{{site.data.alerts.end}}

‎src/current/_includes/v24.2/known-limitations/secondary-regions-with-regional-by-row-tables.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
[Secondary regions]({% link {{ page.version.version }}/multiregion-overview.md %}#secondary-regions) are not compatible with databases containing [`REGIONAL BY ROW`]({% link {{ page.version.version }}/table-localities.md %}#regional-by-row-tables) tables. CockroachDB does not prevent you from defining secondary regions on databases with regional by row tables, but the interaction of these features is not supported.
2+
3+
Therefore, Cockroach Labs recommends that you avoid defining secondary regions on databases that use regional by row table configurations.

‎src/current/_includes/v24.2/sql/regional-by-row-table-description.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,4 +12,8 @@ To take advantage of regional by row tables:
1212

1313
For instructions showing how to set a table's locality to `REGIONAL BY ROW` and configure the home regions of its rows, see [`ALTER TABLE ... SET LOCALITY`]({% link {{ page.version.version }}/alter-table.md %}#crdb_region).
1414

15-
For more information on regional by row tables, see the [Cockroach Labs blog post](https://www.cockroachlabs.com/blog/regional-by-row/).
15+
For more information on regional by row tables, see the [Cockroach Labs blog post](https://www.cockroachlabs.com/blog/regional-by-row/).
16+
17+
{{site.data.alerts.callout_danger}}
18+
{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
19+
{{site.data.alerts.end}}

‎src/current/_includes/v24.3/known-limitations/secondary-regions-with-regional-by-row-tables.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
[Secondary regions]({% link {{ page.version.version }}/multiregion-overview.md %}#secondary-regions) are not compatible with databases containing [`REGIONAL BY ROW`]({% link {{ page.version.version }}/table-localities.md %}#regional-by-row-tables) tables. CockroachDB does not prevent you from defining secondary regions on databases with regional by row tables, but the interaction of these features is not supported.
2+
3+
Therefore, Cockroach Labs recommends that you avoid defining secondary regions on databases that use regional by row table configurations.

‎src/current/_includes/v24.3/sql/regional-by-row-table-description.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,4 +12,8 @@ To take advantage of regional by row tables:
1212

1313
For instructions showing how to set a table's locality to `REGIONAL BY ROW` and configure the home regions of its rows, see [`ALTER TABLE ... SET LOCALITY`]({% link {{ page.version.version }}/alter-table.md %}#crdb_region).
1414

15-
For more information on regional by row tables, see the [Cockroach Labs blog post](https://www.cockroachlabs.com/blog/regional-by-row/).
15+
For more information on regional by row tables, see the [Cockroach Labs blog post](https://www.cockroachlabs.com/blog/regional-by-row/).
16+
17+
{{site.data.alerts.callout_danger}}
18+
{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
19+
{{site.data.alerts.end}}

‎src/current/_includes/v25.1/known-limitations/secondary-regions-with-regional-by-row-tables.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
[Secondary regions]({% link {{ page.version.version }}/multiregion-overview.md %}#secondary-regions) are not compatible with databases containing [`REGIONAL BY ROW`]({% link {{ page.version.version }}/table-localities.md %}#regional-by-row-tables) tables. CockroachDB does not prevent you from defining secondary regions on databases with regional by row tables, but the interaction of these features is not supported.
2+
3+
Therefore, Cockroach Labs recommends that you avoid defining secondary regions on databases that use regional by row table configurations.

‎src/current/_includes/v25.1/sql/regional-by-row-table-description.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,4 +12,8 @@ To take advantage of regional by row tables:
1212

1313
For instructions showing how to set a table's locality to `REGIONAL BY ROW` and configure the home regions of its rows, see [`ALTER TABLE ... SET LOCALITY`]({% link {{ page.version.version }}/alter-table.md %}#crdb_region).
1414

15-
For more information on regional by row tables, see the [Cockroach Labs blog post](https://www.cockroachlabs.com/blog/regional-by-row/).
15+
For more information on regional by row tables, see the [Cockroach Labs blog post](https://www.cockroachlabs.com/blog/regional-by-row/).
16+
17+
{{site.data.alerts.callout_danger}}
18+
{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
19+
{{site.data.alerts.end}}

‎src/current/v23.1/alter-database.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -433,6 +433,8 @@ If the [primary region](#set-primary-region) fails, the secondary region becomes
433433

434434
{{site.data.alerts.callout_danger}}
435435
In order to add a secondary region with `ALTER DATABASE ... SET SECONDARY REGION`, you must first set a primary database region with [`SET PRIMARY REGION`](#set-primary-region), or when [creating the database]({% link {{ page.version.version }}/create-database.md %}). For an example showing how to add a secondary region with `ALTER DATABASE`, see [Set the secondary region](#set-the-secondary-region).
436+
437+
{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
436438
{{site.data.alerts.end}}
437439

438440
For examples, see [Manage regions](#manage-regions).
@@ -550,6 +552,10 @@ ALTER DATABASE SET SECONDARY REGION
550552

551553
Now, the `"us-west1"` region will act as the primary region if the original primary region fails.
552554

555+
{{site.data.alerts.callout_danger}}
556+
{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
557+
{{site.data.alerts.end}}
558+
553559
#### Unset the secondary region
554560

555561
To unset an existing [database region]({% link {{ page.version.version }}/multiregion-overview.md %}#database-regions) as the [secondary region]({% link {{ page.version.version }}/multiregion-overview.md %}#secondary-regions) on a multi-region database, use the [`DROP SECONDARY REGION`](#drop-secondary-region) statement:

‎src/current/v23.1/create-database.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -188,6 +188,10 @@ CREATE DATABASE
188188

189189
For more information about secondary regions, see [Secondary regions]({% link {{ page.version.version }}/multiregion-overview.md %}#secondary-regions).
190190

191+
{{site.data.alerts.callout_danger}}
192+
{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
193+
{{site.data.alerts.end}}
194+
191195
## See also
192196

193197
- [`SHOW DATABASES`]({% link {{ page.version.version }}/show-databases.md %})

‎src/current/v23.1/known-limitations.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -702,6 +702,10 @@ If you think a rollback of a column-dropping schema change has occurred, check t
702702

703703
{% include {{ page.version.version }}/known-limitations/drop-unique-index-from-create-table.md %}
704704

705+
### Secondary regions and regional by row tables
706+
707+
{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
708+
705709
### Row-Level TTL limitations
706710

707711
{% include {{page.version.version}}/known-limitations/row-level-ttl-limitations.md %}

‎src/current/v23.1/migrate-to-multiregion-sql.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -246,6 +246,10 @@ SHOW ZONE CONFIGURATION FROM TABLE users;
246246
247247
~~~
248248

249+
{{site.data.alerts.callout_danger}}
250+
{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
251+
{{site.data.alerts.end}}
252+
249253
#### Global tables
250254

251255
A [`GLOBAL`]({% link {{ page.version.version }}/table-localities.md %}) table differs from the default by setting the following zone configuration settings:

‎src/current/v23.1/multiregion-overview.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -131,6 +131,10 @@ If you are using [super regions](#super-regions) in your cluster, there are addi
131131
</ul>
132132
{{site.data.alerts.end}}
133133

134+
{{site.data.alerts.callout_danger}}
135+
{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
136+
{{site.data.alerts.end}}
137+
134138
## Survival goals
135139

136140
A _survival goal_ dictates how many simultaneous failure(s) a database can survive. All tables within the same database operate with the **same survival goal**. Each database can have its own survival goal setting.

‎src/current/v23.2/alter-database.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -433,6 +433,8 @@ If the [primary region](#set-primary-region) fails, the secondary region becomes
433433

434434
{{site.data.alerts.callout_danger}}
435435
In order to add a secondary region with `ALTER DATABASE ... SET SECONDARY REGION`, you must first set a primary database region with [`SET PRIMARY REGION`](#set-primary-region), or when [creating the database]({% link {{ page.version.version }}/create-database.md %}). For an example showing how to add a secondary region with `ALTER DATABASE`, see [Set the secondary region](#set-the-secondary-region).
436+
437+
{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
436438
{{site.data.alerts.end}}
437439

438440
For examples, see [Manage regions](#manage-regions).
@@ -550,6 +552,10 @@ ALTER DATABASE SET SECONDARY REGION
550552

551553
Now, the `"us-west1"` region will act as the primary region if the original primary region fails.
552554

555+
{{site.data.alerts.callout_danger}}
556+
{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
557+
{{site.data.alerts.end}}
558+
553559
#### Unset the secondary region
554560

555561
To unset an existing [database region]({% link {{ page.version.version }}/multiregion-overview.md %}#database-regions) as the [secondary region]({% link {{ page.version.version }}/multiregion-overview.md %}#secondary-regions) on a multi-region database, use the [`DROP SECONDARY REGION`](#drop-secondary-region) statement:

‎src/current/v23.2/create-database.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -188,6 +188,10 @@ CREATE DATABASE
188188

189189
For more information about secondary regions, see [Secondary regions]({% link {{ page.version.version }}/multiregion-overview.md %}#secondary-regions).
190190

191+
{{site.data.alerts.callout_danger}}
192+
{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
193+
{{site.data.alerts.end}}
194+
191195
## See also
192196

193197
- [`SHOW DATABASES`]({% link {{ page.version.version }}/show-databases.md %})

‎src/current/v23.2/known-limitations.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -701,6 +701,10 @@ This is because the state flip is effected by the CLI program at the end. Only t
701701

702702
{% include {{ page.version.version }}/known-limitations/drop-unique-index-from-create-table.md %}
703703

704+
### Secondary regions and regional by row tables
705+
706+
{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
707+
704708
### Row-Level TTL limitations
705709

706710
{% include {{page.version.version}}/known-limitations/row-level-ttl-limitations.md %}

‎src/current/v23.2/migrate-to-multiregion-sql.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -246,6 +246,10 @@ SHOW ZONE CONFIGURATION FROM TABLE users;
246246
247247
~~~
248248

249+
{{site.data.alerts.callout_danger}}
250+
{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
251+
{{site.data.alerts.end}}
252+
249253
#### Global tables
250254

251255
A [`GLOBAL`]({% link {{ page.version.version }}/table-localities.md %}) table differs from the default by setting the following zone configuration settings:

‎src/current/v23.2/multiregion-overview.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -135,6 +135,10 @@ If you are using [super regions](#super-regions) in your cluster, there are addi
135135
</ul>
136136
{{site.data.alerts.end}}
137137

138+
{{site.data.alerts.callout_danger}}
139+
{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
140+
{{site.data.alerts.end}}
141+
138142
## Survival goals
139143

140144
A _survival goal_ dictates how many simultaneous failure(s) a database can survive. All tables within the same database operate with the **same survival goal**. Each database can have its own survival goal setting.

‎src/current/v24.1/alter-database.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -437,6 +437,8 @@ If the [primary region](#set-primary-region) fails, the secondary region becomes
437437

438438
{{site.data.alerts.callout_danger}}
439439
In order to add a secondary region with `ALTER DATABASE ... SET SECONDARY REGION`, you must first set a primary database region with [`SET PRIMARY REGION`](#set-primary-region), or when [creating the database]({% link {{ page.version.version }}/create-database.md %}). For an example showing how to add a secondary region with `ALTER DATABASE`, see [Set the secondary region](#set-the-secondary-region).
440+
441+
{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
440442
{{site.data.alerts.end}}
441443

442444
For examples, see [Manage regions](#manage-regions).
@@ -554,6 +556,10 @@ ALTER DATABASE SET SECONDARY REGION
554556

555557
Now, the `"us-west1"` region will act as the primary region if the original primary region fails.
556558

559+
{{site.data.alerts.callout_danger}}
560+
{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
561+
{{site.data.alerts.end}}
562+
557563
#### Unset the secondary region
558564

559565
To unset an existing [database region]({% link {{ page.version.version }}/multiregion-overview.md %}#database-regions) as the [secondary region]({% link {{ page.version.version }}/multiregion-overview.md %}#secondary-regions) on a multi-region database, use the [`DROP SECONDARY REGION`](#drop-secondary-region) statement:

‎src/current/v24.1/create-database.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -188,6 +188,10 @@ CREATE DATABASE
188188

189189
For more information about secondary regions, see [Secondary regions]({% link {{ page.version.version }}/multiregion-overview.md %}#secondary-regions).
190190

191+
{{site.data.alerts.callout_danger}}
192+
{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
193+
{{site.data.alerts.end}}
194+
191195
## See also
192196

193197
- [`SHOW DATABASES`]({% link {{ page.version.version }}/show-databases.md %})

‎src/current/v24.1/known-limitations.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -317,6 +317,10 @@ CockroachDB does not allow inverted indexes with a [`STORING` column]({% link {{
317317

318318
{% include {{ page.version.version }}/known-limitations/expression-index-limitations.md %}
319319

320+
#### Secondary regions and regional by row tables
321+
322+
{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
323+
320324
### Data types
321325

322326
#### Spatial support limitations

‎src/current/v24.1/migrate-to-multiregion-sql.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -246,6 +246,10 @@ SHOW ZONE CONFIGURATION FROM TABLE users;
246246
247247
~~~
248248

249+
{{site.data.alerts.callout_danger}}
250+
{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
251+
{{site.data.alerts.end}}
252+
249253
#### Global tables
250254

251255
A [`GLOBAL`]({% link {{ page.version.version }}/table-localities.md %}) table differs from the default by setting the following zone configuration settings:

‎src/current/v24.1/multiregion-overview.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -135,6 +135,10 @@ If you are using [super regions](#super-regions) in your cluster, there are addi
135135
</ul>
136136
{{site.data.alerts.end}}
137137

138+
{{site.data.alerts.callout_danger}}
139+
{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
140+
{{site.data.alerts.end}}
141+
138142
## Survival goals
139143

140144
A _survival goal_ dictates how many simultaneous failure(s) a database can survive. All tables within the same database operate with the **same survival goal**. Each database can have its own survival goal setting.

‎src/current/v24.2/alter-database.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -437,6 +437,8 @@ If the [primary region](#set-primary-region) fails, the secondary region becomes
437437

438438
{{site.data.alerts.callout_danger}}
439439
In order to add a secondary region with `ALTER DATABASE ... SET SECONDARY REGION`, you must first set a primary database region with [`SET PRIMARY REGION`](#set-primary-region), or when [creating the database]({% link {{ page.version.version }}/create-database.md %}). For an example showing how to add a secondary region with `ALTER DATABASE`, see [Set the secondary region](#set-the-secondary-region).
440+
441+
{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
440442
{{site.data.alerts.end}}
441443

442444
For examples, see [Manage regions](#manage-regions).
@@ -554,6 +556,10 @@ ALTER DATABASE SET SECONDARY REGION
554556

555557
Now, the `"us-west1"` region will act as the primary region if the original primary region fails.
556558

559+
{{site.data.alerts.callout_danger}}
560+
{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
561+
{{site.data.alerts.end}}
562+
557563
#### Unset the secondary region
558564

559565
To unset an existing [database region]({% link {{ page.version.version }}/multiregion-overview.md %}#database-regions) as the [secondary region]({% link {{ page.version.version }}/multiregion-overview.md %}#secondary-regions) on a multi-region database, use the [`DROP SECONDARY REGION`](#drop-secondary-region) statement:

‎src/current/v24.2/create-database.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -188,6 +188,10 @@ CREATE DATABASE
188188

189189
For more information about secondary regions, see [Secondary regions]({% link {{ page.version.version }}/multiregion-overview.md %}#secondary-regions).
190190

191+
{{site.data.alerts.callout_danger}}
192+
{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
193+
{{site.data.alerts.end}}
194+
191195
## See also
192196

193197
- [`SHOW DATABASES`]({% link {{ page.version.version }}/show-databases.md %})

‎src/current/v24.2/known-limitations.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -298,6 +298,10 @@ CockroachDB does not allow inverted indexes with a [`STORING` column]({% link {{
298298

299299
{% include {{ page.version.version }}/known-limitations/expression-index-limitations.md %}
300300

301+
#### Secondary regions and regional by row tables
302+
303+
{% include {{page.version.version}}/known-limitations/secondary-regions-with-regional-by-row-tables.md %}
304+
301305
### Data types
302306

303307
#### Spatial support limitations

0 commit comments

Comments
 (0)