Skip to content

Remove outdated line about PCR only being for self-hosted CRDB #19874

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 3, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions src/current/v23.2/physical-cluster-replication-overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,8 +9,6 @@ docs_area: manage
{% include feature-phases/preview.md %}

Refer to the [Known Limitations](#known-limitations) section for further detail.

Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters.
{{site.data.alerts.end}}

{% include_cached new-in.html version="v23.2" %} CockroachDB **physical cluster replication (PCR)** continuously sends all data at the cluster level from a _primary_ cluster to an independent _standby_ cluster. Existing data and ongoing changes on the active primary cluster, which is serving application data, replicate asynchronously to the passive standby cluster.
Expand Down
4 changes: 0 additions & 4 deletions src/current/v24.1/physical-cluster-replication-overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,6 @@ toc: true
docs_area: manage
---

{{site.data.alerts.callout_info}}
Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters.
{{site.data.alerts.end}}

CockroachDB **physical cluster replication (PCR)** continuously sends all data at the cluster level from a _primary_ cluster to an independent _standby_ cluster. Existing data and ongoing changes on the active primary cluster, which is serving application data, replicate asynchronously to the passive standby cluster.

You can [_cut over_]({% link {{ page.version.version }}/cutover-replication.md %}) from the primary cluster to the standby cluster. This will stop the replication stream, reset the standby cluster to a point in time (in the past or future) where all ingested data is consistent, and make the standby ready to accept application traffic.
Expand Down
4 changes: 0 additions & 4 deletions src/current/v24.2/physical-cluster-replication-overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,6 @@ toc: true
docs_area: manage
---

{{site.data.alerts.callout_info}}
Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters.
{{site.data.alerts.end}}

CockroachDB **physical cluster replication (PCR)** continuously sends all data at the cluster level from a _primary_ cluster to an independent _standby_ cluster. Existing data and ongoing changes on the active primary cluster, which is serving application data, replicate asynchronously to the passive standby cluster.

You can [_cut over_]({% link {{ page.version.version }}/cutover-replication.md %}) from the primary cluster to the standby cluster. This will stop the replication stream, reset the standby cluster to a point in time (in the past or future) where all ingested data is consistent, and make the standby ready to accept application traffic.
Expand Down
4 changes: 0 additions & 4 deletions src/current/v24.3/create-virtual-cluster.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,10 +13,6 @@ The `CREATE VIRTUAL CLUSTER` statement creates a new virtual cluster. It is supp

{% include {{ page.version.version }}/physical-replication/phys-rep-sql-pages.md %}

{{site.data.alerts.callout_info}}
Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters.
{{site.data.alerts.end}}

## Required privileges

`CREATE VIRTUAL CLUSTER` requires one of the following privileges:
Expand Down
2 changes: 0 additions & 2 deletions src/current/v24.3/drop-virtual-cluster.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,8 +7,6 @@ docs_area: reference.sql

{{site.data.alerts.callout_info}}
{% include feature-phases/preview.md %}

Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters.
{{site.data.alerts.end}}

The `DROP VIRTUAL CLUSTER` statement removes virtual clusters in order to restart a **physical cluster replication (PCR)** stream. Virtual clusters are used only as part of the [PCR]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) workflow.
Expand Down
4 changes: 0 additions & 4 deletions src/current/v24.3/physical-cluster-replication-monitoring.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,6 @@ toc: true
docs_area: manage
---

{{site.data.alerts.callout_info}}
Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters.
{{site.data.alerts.end}}

You can monitor a [**physical cluster replication (PCR)**]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) stream using:

- [`SHOW VIRTUAL CLUSTER ... WITH REPLICATION STATUS`](#sql-shell) in the SQL shell.
Expand Down
4 changes: 0 additions & 4 deletions src/current/v24.3/physical-cluster-replication-overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,6 @@ toc: true
docs_area: manage
---

{{site.data.alerts.callout_info}}
Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters.
{{site.data.alerts.end}}

CockroachDB **physical cluster replication (PCR)** continuously sends all data at the cluster level from a _primary_ cluster to an independent _standby_ cluster. Existing data and ongoing changes on the active primary cluster, which is serving application data, replicate asynchronously to the passive standby cluster.

You can [_fail over_]({% link {{ page.version.version }}/failover-replication.md %}) from the primary cluster to the standby cluster. This will stop the replication stream, reset the standby cluster to a point in time (in the past or future) where all ingested data is consistent, and make the standby ready to accept application traffic.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,6 @@ toc: true
docs_area: manage
---

{{site.data.alerts.callout_info}}
Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters.
{{site.data.alerts.end}}

[**Physical cluster replication (PCR)**]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) automatically and continuously streams data from an active _primary_ CockroachDB cluster to a passive _standby_ cluster. Each cluster contains: a _system virtual cluster_ and an application [virtual cluster]({% link {{ page.version.version }}/cluster-virtualization-overview.md %}):

{% include {{ page.version.version }}/physical-replication/interface-virtual-cluster.md %}
Expand Down
4 changes: 0 additions & 4 deletions src/current/v24.3/set-up-physical-cluster-replication.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,6 @@ toc: true
docs_area: manage
---

{{site.data.alerts.callout_info}}
Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters.
{{site.data.alerts.end}}

In this tutorial, you will set up [**physical cluster replication (PCR)**]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) between a primary cluster and standby cluster. The primary cluster is _active_, serving application traffic. The standby cluster is _passive_, accepting updates from the primary cluster. The replication stream will send changes from the primary to the standby.

The unit of replication is a [virtual cluster]({% link {{ page.version.version }}/cluster-virtualization-overview.md %}), which is part of the underlying infrastructure in the primary and standby clusters.
Expand Down
4 changes: 0 additions & 4 deletions src/current/v25.1/create-virtual-cluster.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,10 +13,6 @@ The `CREATE VIRTUAL CLUSTER` statement creates a new virtual cluster. It is supp

{% include {{ page.version.version }}/physical-replication/phys-rep-sql-pages.md %}

{{site.data.alerts.callout_info}}
Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters.
{{site.data.alerts.end}}

## Required privileges

`CREATE VIRTUAL CLUSTER` requires one of the following privileges:
Expand Down
2 changes: 0 additions & 2 deletions src/current/v25.1/drop-virtual-cluster.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,8 +7,6 @@ docs_area: reference.sql

{{site.data.alerts.callout_info}}
{% include feature-phases/preview.md %}

Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters.
{{site.data.alerts.end}}

The `DROP VIRTUAL CLUSTER` statement removes virtual clusters in order to restart a **physical cluster replication (PCR)** stream. Virtual clusters are used only as part of the [PCR]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) workflow.
Expand Down
4 changes: 0 additions & 4 deletions src/current/v25.1/physical-cluster-replication-monitoring.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,6 @@ toc: true
docs_area: manage
---

{{site.data.alerts.callout_info}}
Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters.
{{site.data.alerts.end}}

You can monitor a [**physical cluster replication (PCR)**]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) stream using:

- [`SHOW VIRTUAL CLUSTER ... WITH REPLICATION STATUS`](#sql-shell) in the SQL shell.
Expand Down
4 changes: 0 additions & 4 deletions src/current/v25.1/physical-cluster-replication-overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,6 @@ toc: true
docs_area: manage
---

{{site.data.alerts.callout_info}}
Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters.
{{site.data.alerts.end}}

CockroachDB **physical cluster replication (PCR)** continuously sends all data at the cluster level from a _primary_ cluster to an independent _standby_ cluster. Existing data and ongoing changes on the active primary cluster, which is serving application data, replicate asynchronously to the passive standby cluster.

You can [_fail over_]({% link {{ page.version.version }}/failover-replication.md %}) from the primary cluster to the standby cluster. This will stop the replication stream, reset the standby cluster to a point in time (in the past or future) where all ingested data is consistent, and make the standby ready to accept application traffic.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,6 @@ toc: true
docs_area: manage
---

{{site.data.alerts.callout_info}}
Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters.
{{site.data.alerts.end}}

[**Physical cluster replication (PCR)**]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) automatically and continuously streams data from an active _primary_ CockroachDB cluster to a passive _standby_ cluster. Each cluster contains: a _system virtual cluster_ and an application [virtual cluster]({% link {{ page.version.version }}/cluster-virtualization-overview.md %}) during the PCR stream:

{% include {{ page.version.version }}/physical-replication/interface-virtual-cluster.md %}
Expand Down
4 changes: 0 additions & 4 deletions src/current/v25.1/set-up-physical-cluster-replication.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,6 @@ toc: true
docs_area: manage
---

{{site.data.alerts.callout_info}}
Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters.
{{site.data.alerts.end}}

In this tutorial, you will set up [**physical cluster replication (PCR)**]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) between a primary cluster and standby cluster. The primary cluster is _active_, serving application traffic. The standby cluster is _passive_, accepting updates from the primary cluster. The replication stream will send changes from the primary to the standby.

The unit of replication is a [virtual cluster]({% link {{ page.version.version }}/cluster-virtualization-overview.md %}), which is part of the underlying infrastructure in the primary and standby clusters.
Expand Down
4 changes: 0 additions & 4 deletions src/current/v25.2/create-virtual-cluster.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,10 +13,6 @@ The `CREATE VIRTUAL CLUSTER` statement creates a new virtual cluster. It is supp

{% include {{ page.version.version }}/physical-replication/phys-rep-sql-pages.md %}

{{site.data.alerts.callout_info}}
Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters.
{{site.data.alerts.end}}

## Required privileges

{% include_cached new-in.html version="v25.2" %} The following [privileges]({% link {{ page.version.version }}/security-reference/authorization.md %}#supported-privileges) are required to start a PCR stream with `CREATE VIRTUAL CLUSTER`:
Expand Down
2 changes: 0 additions & 2 deletions src/current/v25.2/drop-virtual-cluster.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,8 +7,6 @@ docs_area: reference.sql

{{site.data.alerts.callout_info}}
{% include feature-phases/preview.md %}

Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters.
{{site.data.alerts.end}}

The `DROP VIRTUAL CLUSTER` statement removes virtual clusters in order to restart a **physical cluster replication (PCR)** stream. Virtual clusters are used only as part of the [PCR]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) workflow.
Expand Down
4 changes: 0 additions & 4 deletions src/current/v25.2/physical-cluster-replication-monitoring.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,6 @@ toc: true
docs_area: manage
---

{{site.data.alerts.callout_info}}
Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters.
{{site.data.alerts.end}}

You can monitor a [**physical cluster replication (PCR)**]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) stream using:

- [`SHOW VIRTUAL CLUSTER ... WITH REPLICATION STATUS`](#sql-shell) in the SQL shell.
Expand Down
4 changes: 0 additions & 4 deletions src/current/v25.2/physical-cluster-replication-overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,6 @@ toc: true
docs_area: manage
---

{{site.data.alerts.callout_info}}
Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters.
{{site.data.alerts.end}}

CockroachDB **physical cluster replication (PCR)** continuously sends all data at the cluster level from a _primary_ cluster to an independent _standby_ cluster. Existing data and ongoing changes on the active primary cluster, which is serving application data, replicate asynchronously to the passive standby cluster.

You can [_fail over_]({% link {{ page.version.version }}/failover-replication.md %}) from the primary cluster to the standby cluster. This will stop the replication stream, reset the standby cluster to a point in time (in the past or future) where all ingested data is consistent, and make the standby ready to accept application traffic.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,6 @@ toc: true
docs_area: manage
---

{{site.data.alerts.callout_info}}
Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters.
{{site.data.alerts.end}}

[**Physical cluster replication (PCR)**]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) automatically and continuously streams data from an active _primary_ CockroachDB cluster to a passive _standby_ cluster. Each cluster contains: a _system virtual cluster_ and an application [virtual cluster]({% link {{ page.version.version }}/cluster-virtualization-overview.md %}) during the PCR stream:

{% include {{ page.version.version }}/physical-replication/interface-virtual-cluster.md %}
Expand Down
4 changes: 0 additions & 4 deletions src/current/v25.2/set-up-physical-cluster-replication.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,6 @@ toc: true
docs_area: manage
---

{{site.data.alerts.callout_info}}
Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters.
{{site.data.alerts.end}}

In this tutorial, you will set up [**physical cluster replication (PCR)**]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) between a primary cluster and standby cluster. The primary cluster is _active_, serving application traffic. The standby cluster is _passive_, accepting updates from the primary cluster. The replication stream will send changes from the primary to the standby.

The unit of replication is a [virtual cluster]({% link {{ page.version.version }}/cluster-virtualization-overview.md %}), which is part of the underlying infrastructure in the primary and standby clusters.
Expand Down
4 changes: 0 additions & 4 deletions src/current/v25.3/create-virtual-cluster.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,10 +13,6 @@ The `CREATE VIRTUAL CLUSTER` statement creates a new virtual cluster. It is supp

{% include {{ page.version.version }}/physical-replication/phys-rep-sql-pages.md %}

{{site.data.alerts.callout_info}}
Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters.
{{site.data.alerts.end}}

## Required privileges

The following [privileges]({% link {{ page.version.version }}/security-reference/authorization.md %}#supported-privileges) are required to start a PCR stream with `CREATE VIRTUAL CLUSTER`:
Expand Down
2 changes: 0 additions & 2 deletions src/current/v25.3/drop-virtual-cluster.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,8 +7,6 @@ docs_area: reference.sql

{{site.data.alerts.callout_info}}
{% include feature-phases/preview.md %}

Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters.
{{site.data.alerts.end}}

The `DROP VIRTUAL CLUSTER` statement removes virtual clusters in order to restart a **physical cluster replication (PCR)** stream. Virtual clusters are used only as part of the [PCR]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) workflow.
Expand Down
4 changes: 0 additions & 4 deletions src/current/v25.3/physical-cluster-replication-monitoring.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,6 @@ toc: true
docs_area: manage
---

{{site.data.alerts.callout_info}}
Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters.
{{site.data.alerts.end}}

You can monitor a [**physical cluster replication (PCR)**]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) stream using:

- [`SHOW VIRTUAL CLUSTER ... WITH REPLICATION STATUS`](#sql-shell) in the SQL shell.
Expand Down
4 changes: 0 additions & 4 deletions src/current/v25.3/physical-cluster-replication-overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,6 @@ toc: true
docs_area: manage
---

{{site.data.alerts.callout_info}}
Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters.
{{site.data.alerts.end}}

CockroachDB **physical cluster replication (PCR)** continuously sends all data at the cluster level from a _primary_ cluster to an independent _standby_ cluster. Existing data and ongoing changes on the active primary cluster, which is serving application data, replicate asynchronously to the passive standby cluster.

You can [_fail over_]({% link {{ page.version.version }}/failover-replication.md %}) from the primary cluster to the standby cluster. This will stop the replication stream, reset the standby cluster to a point in time (in the past or future) where all ingested data is consistent, and make the standby ready to accept application traffic.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,6 @@ toc: true
docs_area: manage
---

{{site.data.alerts.callout_info}}
Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters.
{{site.data.alerts.end}}

[**Physical cluster replication (PCR)**]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) automatically and continuously streams data from an active _primary_ CockroachDB cluster to a passive _standby_ cluster. Each cluster contains: a _system virtual cluster_ and an application [virtual cluster]({% link {{ page.version.version }}/cluster-virtualization-overview.md %}) during the PCR stream:

{% include {{ page.version.version }}/physical-replication/interface-virtual-cluster.md %}
Expand Down
4 changes: 0 additions & 4 deletions src/current/v25.3/set-up-physical-cluster-replication.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,6 @@ toc: true
docs_area: manage
---

{{site.data.alerts.callout_info}}
Physical cluster replication is only supported in CockroachDB {{ site.data.products.core }} clusters.
{{site.data.alerts.end}}

In this tutorial, you will set up [**physical cluster replication (PCR)**]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) between a primary cluster and standby cluster. The primary cluster is _active_, serving application traffic. The standby cluster is _passive_, accepting updates from the primary cluster. The replication stream will send changes from the primary to the standby.

The unit of replication is a [virtual cluster]({% link {{ page.version.version }}/cluster-virtualization-overview.md %}), which is part of the underlying infrastructure in the primary and standby clusters.
Expand Down
Loading