From 313d4509b1f45bbd4d2dd2eb26f72cb3dd42fdc4 Mon Sep 17 00:00:00 2001 From: Rich Loveland Date: Fri, 15 Nov 2024 15:30:08 -0500 Subject: [PATCH] Fix another merge skew thing "Self-Hosted" came back even though it was killed in https://github.com/cockroachdb/docs/pull/19083 --- src/current/v23.2/cockroachdb-feature-availability.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/current/v23.2/cockroachdb-feature-availability.md b/src/current/v23.2/cockroachdb-feature-availability.md index 76bd4ed3b97..688c3c2fede 100644 --- a/src/current/v23.2/cockroachdb-feature-availability.md +++ b/src/current/v23.2/cockroachdb-feature-availability.md @@ -248,7 +248,7 @@ The multiple active portals feature of the Postgres wire protocol (pgwire) is av ### Physical Cluster Replication -{% include_cached new-in.html version="v23.2" %}[Physical cluster replication]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) continuously sends all data at the byte 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. In a disaster recovery scenario, you can cut over from the unavailable primary cluster to the standby cluster. This will stop the replication stream, reset the standby cluster to a point in time where all ingested data is consistent, and mark the standby as ready to accept application traffic. Physical cluster replication is in preview for CockroachDB Self-Hosted. +{% include_cached new-in.html version="v23.2" %}[Physical cluster replication]({% link {{ page.version.version }}/physical-cluster-replication-overview.md %}) continuously sends all data at the byte 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. In a disaster recovery scenario, you can cut over from the unavailable primary cluster to the standby cluster. This will stop the replication stream, reset the standby cluster to a point in time where all ingested data is consistent, and mark the standby as ready to accept application traffic. Physical cluster replication is in preview for CockroachDB {{ site.data.products.core }} clusters. ### Super regions