From 3be704981818d86eb8324745f1c5300adf976a47 Mon Sep 17 00:00:00 2001 From: Josh Earlenbaugh Date: Tue, 14 Jan 2025 11:48:52 -0500 Subject: [PATCH] Fixed image call --- product_docs/docs/pgd/5.6/overview/basic-architecture.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5.6/overview/basic-architecture.mdx b/product_docs/docs/pgd/5.6/overview/basic-architecture.mdx index f6d5cbb5b87..f305edb5c6c 100644 --- a/product_docs/docs/pgd/5.6/overview/basic-architecture.mdx +++ b/product_docs/docs/pgd/5.6/overview/basic-architecture.mdx @@ -36,7 +36,7 @@ At the highest level, PGD comprises two main components: Bi-Directional Replicat BDR is a Postgres extension that enables a multi-master replication mesh between different BDR-enabled Postgres instances/nodes. [PGD proxy](../routing) sends requests to the write leader—ensuring a lower risk of conflicts between nodes. -![Diagram showing 3 application nodes, 3 proxy instances, and 3 PGD nodes. Traffic is being directed from each of the proxy instances to the write leader node.](/docs/product_docs/docs/pgd/5.6/overview/img/always_on_1x3_updated.png) +![Diagram showing 3 application nodes, 3 proxy instances, and 3 PGD nodes. Traffic is being directed from each of the proxy instances to the write leader node.](./img/always_on_1x3_updated.png) Changes are replicated directly, row-by-row between all nodes. [Logical replication](../terminology/#logical-replication) in PGD is asynchronous by default, so only eventual consistency is guaranteed (within seconds usually).