Skip to content

Commit 544bc9d

Browse files
irionririonr
committed
[Future PGD 6.2.0] Add 6.2 directory
1 parent 47c4d19 commit 544bc9d

File tree

304 files changed

+30132
-0
lines changed

Some content is hidden

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

304 files changed

+30132
-0
lines changed

‎product_docs/docs/pgd/6.2/compatibility.mdx‎

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
---
2+
title: PGD compatibility
3+
navTitle: Compatibility
4+
description: Compatibility of EDB Postgres Distributed with different versions of PostgreSQL
5+
deepToC: true
6+
---
7+
8+
## PGD compatibility with PostgreSQL versions
9+
10+
The following table shows the major versions of PostgreSQL that EDB Postgres Distributed (PGD) is compatible with.
11+
12+
| PGD 6 | Postgres Version |
13+
|-------------|------------------|
14+
| [6](/pgd/6.1/) | 17.5.0+ |
15+
| [6](/pgd/6.1/) | 16.9.0+ |
16+
| [6](/pgd/6.1/) | 15.13.0+ |
17+
| [6](/pgd/6.1/) | 14.18.0+ |
18+
19+
EDB recommends that you use the latest minor version of any Postgres major version with a supported PGD.
20+
21+
## PGD compatibility with operating systems and architectures
22+
23+
The following tables show the versions of EDB Postgres Distributed and their compatibility with various operating systems and architectures.
24+
25+
### Linux
26+
27+
| Operating System | x86_64<br/>(amd64) | ppc64le | arm64/<br/>aarch64 |
28+
|------------------------------------|----------------|---------|---------------|
29+
| RHEL 8 | Yes | Yes | |
30+
| RHEL 9 | Yes | Yes | Yes |
31+
| Oracle Linux 8 | Yes | | |
32+
| Oracle Linux 9 | Yes | | |
33+
| Rocky Linux/AlmaLinux | Yes | | |
34+
| SUSE Linux Enterprise Server 15SP6 | Yes | Yes | |
35+
| Ubuntu 22.04 | Yes | | |
36+
| Ubuntu 24.04 | Yes | | |
37+
| Debian 12 | Yes | | Yes |
38+
| IBM Linux One | Yes | | |
39+
40+
!!! Note
41+
See [PGD 5 Compatibility](/pgd/5.8/compatibility) for previous versions of PGD.
42+
!!!

‎product_docs/docs/pgd/6.2/concepts/advanced-durability.mdx‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
---
2+
title: Advanced Durability
3+
---
4+

‎product_docs/docs/pgd/6.2/concepts/commit-scopes.mdx‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
---
2+
title: Commit Scopes
3+
---
4+

‎product_docs/docs/pgd/6.2/concepts/conflict-management.mdx‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
---
2+
title: Conflict Management
3+
---
4+
5+
With PGD Expanded, the presence of multiple writers leads to the possibility, or even the likelihood, of conflicts. Changes to the same rows from different nodes can arrive on a node at any time.
6+
PGD Expanded provides a conflict management system that allows you to define how conflicts are handled in your distributed database environment.
7+
8+
Read more about conflict management in the [Conflict Management reference](/pgd/latest/reference/conflict-management/) documentation.
9+

‎product_docs/docs/pgd/6.2/concepts/connection-management.mdx‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
---
2+
title: Connection Management
3+
---
4+
5+
To ensure that clients can connect to the right nodes in the distributed cluster, EDB Postgres Distributed (PGD) provides a connection management system that allows clients to connect to the appropriate nodes based on their needs.
6+
7+
This system is designed to ensure that clients can access the data they need while maintaining the performance and availability of the cluster.
8+
Unlike Proxy systems, this connection management system is built into the database instance itself, allowing for more efficient and reliable connections.
9+
10+
Read more about the [Connection Management feature in PGD](/pgd/latest/reference/connection-manager/) for full details of the implementation.
11+

‎product_docs/docs/pgd/6.2/concepts/durability.mdx‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
---
2+
title: Durability
3+
---
4+
5+
How does EDB Postgres Distributed (PGD) ensure durability of transactions?
6+
7+
Durability can be defined as the guarantee that once a transaction has been committed, it will remain so, even in the event of a system failure. In EDB Postgres Distributed (PGD), durability is achieved through a combination of write-ahead logging (WAL) and replication, in combination with the commit scopes available in the cluster and the configuration of the nodes in the cluster.
8+

‎product_docs/docs/pgd/6.2/concepts/expanded-commit-scopes.mdx‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
---
2+
title: Expanded Commit Scopes
3+
---
4+
5+
PGD Expanded allows you to define commit scopes that are more granular or more customised than the standard pre-defined commit scopes available in PGD. This feature is particularly useful for applications that require specific commit behaviors or need to manage complex transaction scenarios.
6+

‎product_docs/docs/pgd/6.2/concepts/geo-distributed-clusters.mdx‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
---
2+
title: Geo-Distributed Clusters
3+
---
4+
5+
Geo-distributed clusters are a powerful feature of PGD which allow you to create a distributed database system that spans multiple geographic locations. This setup is particularly useful for applications that require high availability, low latency, and disaster recovery across different regions. As this feature needs multiple write nodes and multiple distributed groups, it is only available in PGD Expanded.
6+

‎product_docs/docs/pgd/6.2/concepts/index.mdx‎

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
---
2+
title: PGD concepts explained
3+
navTitle: PGD concepts explained
4+
description: The concepts behind EDB Postgres Distributed (PGD) 6.0 and how they work in practice.
5+
navigation:
6+
- replication
7+
- nodes-and-groups
8+
- connection-management
9+
- locking
10+
- durability
11+
- commit-scopes
12+
- lag-control
13+
- expanded-commit-scopes
14+
- geo-distributed-clusters
15+
- advanced-durability
16+
- conflict-management
17+
---
18+
19+
## PGD concepts
20+
21+
* [Replication](replication)
22+
* [Nodes and groups](nodes-and-groups)
23+
* [Connection management](connection-management)
24+
* [Locking](locking)
25+
* [Durability](durability)
26+
* [Commit scopes](commit-scopes)
27+
* [Lag Control](lag-control)
28+
29+
## PGD Expanded concepts
30+
31+
* [Commit scopes for PGD Expanded](expanded-commit-scopes)
32+
* [Geo-distributed clusters](geo-distributed-clusters)
33+
* [Advanced durability](advanced-durability)
34+
* [Conflict management](conflict-management)

‎product_docs/docs/pgd/6.2/concepts/lag-control.mdx‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
---
2+
title: Lag Control
3+
---
4+
5+
When a node is lagging behind the rest of the cluster, it can cause issues with data consistency and availability. Lag control is a mechanism to manage this situation by ensuring that the lagging node does not disrupt the overall performance of the cluster.
6+
7+
## Lag Control in PGD
8+
9+
When lag is detected in PGD, the Lag Control feature is activated. This feature is designed to manage the lagging node and ensure that it does not disrupt the overall performance of the cluster. It does this by transparently and temporarily slowing client connections, introducing a commit delay to clients. This allows the lagging node to catch up with the rest of the cluster without impacting the performance of the other nodes.
10+
11+
Read more about the [Lag Control feature in PGD](/pgd/latest/reference/commit-scopes/lag-control/) for full details.

0 commit comments

Comments
 (0)