Place known limitations

cockroachdb · May 15, 2024 · e37f4d2 · e37f4d2
1 parent d422d1d
commit e37f4d2
Show file tree

Hide file tree

Showing 6 changed files with 8 additions and 1 deletion.
diff --git a/src/current/v23.2/create-and-configure-changefeeds.md b/src/current/v23.2/create-and-configure-changefeeds.md
@@ -180,6 +180,7 @@ For more information, see [`EXPERIMENTAL CHANGEFEED FOR`]({% link {{ page.versio
 ## Known limitations
 
 {% include {{ page.version.version }}/known-limitations/cdc.md %}
+- {% include {{ page.version.version }}/known-limitations/pcr-scheduled-changefeeds.md %}
 
 ## See also
 

diff --git a/src/current/v23.2/known-limitations.md b/src/current/v23.2/known-limitations.md
@@ -73,7 +73,8 @@ This page describes newly identified limitations in the CockroachDB {{page.relea
 
 ### Physical cluster replication
 
-{% include {{ page.version.version }}/known-limitations/pcr-scheduled-changefeeds.md %}
+{% include {{ page.version.version }}/known-limitations/physical-cluster-replication.md %}
+- {% include {{ page.version.version }}/known-limitations/pcr-scheduled-changefeeds.md %}
 
 ## Unresolved limitations
 

diff --git a/src/current/v23.2/physical-cluster-replication-overview.md b/src/current/v23.2/physical-cluster-replication-overview.md
@@ -42,6 +42,7 @@ You can use physical cluster replication in a disaster recovery plan to:
 ## Known limitations
 
 {% include {{ page.version.version }}/known-limitations/physical-cluster-replication.md %}
+- {% include {{ page.version.version }}/known-limitations/pcr-scheduled-changefeeds.md %}
 
 ## Get started
 

diff --git a/src/current/v24.1/create-and-configure-changefeeds.md b/src/current/v24.1/create-and-configure-changefeeds.md
@@ -180,6 +180,7 @@ For more information, see [`EXPERIMENTAL CHANGEFEED FOR`]({% link {{ page.versio
 ## Known limitations
 
 {% include {{ page.version.version }}/known-limitations/cdc.md %}
+- {% include {{ page.version.version }}/known-limitations/pcr-scheduled-changefeeds.md %}
 
 ## See also
 

diff --git a/src/current/v24.1/known-limitations.md b/src/current/v24.1/known-limitations.md
@@ -399,6 +399,7 @@ Accessing the DB Console for a secure cluster now requires login information (i.
 #### Physical cluster replication
 
 {% include {{ page.version.version }}/known-limitations/physical-cluster-replication.md %}
+- {% include {{ page.version.version }}/known-limitations/pcr-scheduled-changefeeds.md %}
 
 #### Table-level restore will not restore user-defined functions
 
@@ -421,6 +422,7 @@ As a workaround, take a cluster backup instead, as the `system.comments` table i
 Change data capture (CDC) provides efficient, distributed, row-level changefeeds into Apache Kafka for downstream processing such as reporting, caching, or full-text indexing. It has the following known limitations:
 
 {% include {{ page.version.version }}/known-limitations/cdc.md %}
+- {% include {{ page.version.version }}/known-limitations/pcr-scheduled-changefeeds.md %}
 {% include {{ page.version.version }}/known-limitations/cdc-queries.md %}
 
 #### `ALTER CHANGEFEED` limitations

diff --git a/src/current/v24.1/physical-cluster-replication-overview.md b/src/current/v24.1/physical-cluster-replication-overview.md
@@ -42,6 +42,7 @@ You can use physical cluster replication in a disaster recovery plan to:
 ## Known limitations
 
 {% include {{ page.version.version }}/known-limitations/physical-cluster-replication.md %}
+- {% include {{ page.version.version }}/known-limitations/pcr-scheduled-changefeeds.md %}
 
 ## Get started