Skip to content

Commit

Permalink
Merge pull request #3722 from EnterpriseDB/release/2023-02-23
Browse files Browse the repository at this point in the history 
Release: 2023-02-23
  • Loading branch information
@drothery-edb
drothery-edb authored Feb 23, 2023
2 parents 64f5822 + 53d10b2 commit b042d3e
Show file tree
Hide file tree
Showing 8 changed files with 61 additions and 43 deletions.
14 changes: 14 additions & 0 deletions product_docs/docs/pgd/5/durability/camo.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -157,6 +157,20 @@ provide some detail.
This example considers a setup with two PGD nodes that are the
CAMO partner of each other.

```sql
-- create a CAMO commit scope for a group over
-- a definite pair of nodes
SELECT bdr.add_commit_scope(
commit_scope_name := 'example_scope',
origin_node_group := 'camo_dc',
rule := 'ALL (left_dc) CAMO DEGRADE ON (timeout=500ms) TO ASYNC'
);
```
For this CAMO commit scope to be legal, the number of nodes in the group
must equal exactly 2. Using ALL or ANY 2 on a group consisting of several
nodes is an error because the unquantified group expression does not resolve
to a definite pair of nodes.

#### With asynchronous mode

If asynchronous mode is allowed, there's no single point of failure. When one
Expand Down
4 changes: 2 additions & 2 deletions product_docs/docs/pgd/5/durability/commit-scopes.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -79,13 +79,13 @@ SELECT bdr.create_node_group(
SELECT bdr.add_commit_scope(
commit_scope_name := 'example_scope',
origin_node_group := 'left_dc',
rule := 'ALL (left_dc) AND ANY 1 (right_dc)',
rule := 'ALL (left_dc) GROUP COMMIT AND ANY 1 (right_dc) GROUP COMMIT',
wait_for_ready := true
);
SELECT bdr.add_commit_scope(
commit_scope_name := 'example_scope',
origin_node_group := 'right_dc',
rule := 'ANY 1 (left_dc) AND ALL (right_dc)',
rule := 'ANY 1 (left_dc) GROUP COMMIT AND ALL (right_dc) GROUP COMMIT',
wait_for_ready := true
);
```
Expand Down
6 changes: 3 additions & 3 deletions product_docs/docs/pgd/5/durability/lag-control.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -62,18 +62,18 @@ Lag control is specified within a commit scope, which allows consistent and coo
Using the sample node groups from the [Commit Scope](commit-scopes) chapter, this example shows lag control rules for two datacenters.

```sql
-- create a Lag control commit scope with individual rules
-- create a Lag Control commit scope with individual rules
-- for each sub-group
SELECT bdr.add_commit_scope(
commit_scope_name := 'example_scope',
origin_node_group := 'left_dc',
rule := 'ALL (left_dc) AND ANY 1 (right_dc) LAG CONTROL (max_commit_delay=500ms, max_lag_time=30s)',
rule := 'ALL (left_dc) LAG CONTROL (max_commit_delay=500ms, max_lag_time=30s) AND ANY 1 (right_dc) LAG CONTROL (max_commit_delay=500ms, max_lag_time=30s)',
wait_for_ready := true
);
SELECT bdr.add_commit_scope(
commit_scope_name := 'example_scope',
origin_node_group := 'right_dc',
rule := 'ANY 1 (left_dc) AND ALL (right_dc) LAG CONTROL (max_commit_delay=0.250ms, max_lag_size=100MB)',
rule := 'ANY 1 (left_dc) LAG CONTROL (max_commit_delay=0.250ms, max_lag_size=100MB) AND ALL (right_dc) LAG CONTROL (max_commit_delay=0.250ms, max_lag_size=100MB)',
wait_for_ready := true
);
```
Expand Down
2 changes: 1 addition & 1 deletion product_docs/docs/pgd/5/rel_notes/pgd_5.0.0_rel_notes.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ The highlights of this release include:
| BDR | 5.0.0 | Feature | Postgres 15 compatibility <p> EDB Postgres Distributed 5 is compatible with Postgres 12 to 15. </p> |
| BDR | 5.0.0 | Feature | Improved Cluster Event Management <p> The `bdr.worker_errors` and `bdr.state_journal_details` view were replaced by unified `bdr.event_summary` which also include changes in Raft role for the local node. In the future additional events may be added to it. </p> |
| BDR | 5.0.0 | Change | Improved transaction tracking performance <p> Transaction tracking now uses shared memory instead of `bdr.internal_node_pre_commit` catalog which considerably improves performance as it does not incur additional I/O. </p> |
| BDR | 5.0.0 | Feature | Support non-default replication sets with Decoding Worker <p> Allows Decoding Worker feature to be used in clusters using non-default replication sets like assymetric replication setup. </p> |
| BDR | 5.0.0 | Feature | Support non-default replication sets with Decoding Worker <p> Allows Decoding Worker feature to be used in clusters using non-default replication sets like asymmetric replication setup. </p> |
| BDR | 5.0.0 | Feature | Add support for HASH partitioning in Autopartition <p> Extend autopartition/autoscale to support HASH partitioning. Many of things that are required for RANGE partitioning are not needed for HASH partitioning. For example, we expect to create all HASH partitions in one go (at least for the current work; later we may change this). We don't expect HASH partitions to be moved to a different tablespace or dropped. So data retention policies don't apply for HASH partitioning. </p> |
| BDR | 5.0.0 | Feature | Add a new benchmarking utility `pgd_bench` <p> The utility supports benchmarking CAMO transactions and in future releases will be used for benchmarking PGD specific workloads. </p> |
| BDR | 5.0.0 | Change | Separate Task Management from Autopartition <p> In this release, the autopartition work queue mechanism has been moved to a separate module called Task Manager (taskmgr). The task manager is responsible for creating new tasks and executing the ones created by the local node or the task manager leader node. The autopartition worker is thus renamed as taskmgr worker process in this release. </p> <p> In the older PGD releases, the Raft leader was responsible for creating new work items. But that creates a problem because a witness node can become a Raft leader while it does not have the full view of the cluster objects. In this release, we have introduced a concept of Task Manager Leader node. The node is selected automatically by PGD, but for upgraded clusters, its important to set the `node_kind` properly for all nodes in the cluster. The user is expected to this manually after upgrading to the latest PGD version by calling bdr.alter_node_kind() SQL function for each node. </p> |
Expand Down
6 changes: 3 additions & 3 deletions product_docs/docs/tpa/23/reference/INSTALL-docker.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ Double-check the created image:
$ docker image ls tpa/tpaexec
REPOSITORY TAG IMAGE ID CREATED SIZE
tpa/tpaexec latest e145cf8276fb 8 seconds ago 1.73GB
$ docker run --rm tpa/tpaexec tpaexec info
$ docker run --platform=linux/amd64 --rm tpa/tpaexec tpaexec info
# TPAexec v20.11-59-g85a62fe3 (branch: master)
tpaexec=/usr/local/bin/tpaexec
TPA_DIR=/opt/EDB/TPA
Expand All @@ -46,7 +46,7 @@ Create a TPA container and make your cluster configuration directories
available inside the container:

```bash
$ docker run --rm -v ~/clusters:/clusters \
$ docker run --platform=linux/amd64 --rm -v ~/clusters:/clusters \
-it tpa/tpaexec:latest
```

Expand All @@ -57,7 +57,7 @@ If you want to provision Docker containers using TPA, you must also allow
the container to access the Docker control socket on the host:

```
$ docker run --rm -v ~/clusters:/clusters \
$ docker run --platform=linux/amd64 --rm -v ~/clusters:/clusters \
-v /var/run/docker.sock:/var/run/docker.sock \
-it tpa/tpaexec:latest
```
Expand Down
7 changes: 6 additions & 1 deletion product_docs/docs/tpa/23/rel_notes/index.mdx
View file
Original file line number Diff line number Diff line change
@@ -1,10 +1,15 @@
---
title: "Release notes"
title: Trusted Postgres Architect release notes
navTitle: "Release notes"
navigation:
- tpa_23.13_rel_notes
- tpa_23.12_rel_notes
---

The Trusted Postgres Architect documentation describes the latest version of Trusted Postgres Architect 23.

| Version | Release date |
| ------- | ------------ |
| [23.13](tpa_23.13_rel_notes) | 22 Feb 2023 |
| [23.12](tpa_23.12_rel_notes) | 21 Feb 2023 |

13 changes: 13 additions & 0 deletions product_docs/docs/tpa/23/rel_notes/tpa_23.13_rel_notes.mdx
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
---
title: Trusted Postgres Architect 23.13 release notes
navTitle: "Version 23.13"
---


New features, enhancements, bug fixes, and other changes in Trusted Postgres Architect 23.13 include the following:

| Type | Description |
| ---- |------------ |
| Bug fix | Don't enable old EDB repo with PGD-Always-ON and `--epas`. |
| Bug fix | Fix error with PGD-Always-ON and `--postgres-version 15`. |

52 changes: 19 additions & 33 deletions src/pages/index.js
View file
Original file line number Diff line number Diff line change
Expand Up @@ -47,36 +47,34 @@ const Page = () => (
<div className="col-sm mb-3 mr-1">
<div className="mb-2">
<div className="new-thing-header" aria-roledescription="badge">
<span className="badge-text font-weight-bold">Demo</span>
<span className="badge-text font-weight-bold">
What's new
</span>
</div>
</div>

<div className="mb-3">
<h3 className="card-title mb-2 font-weight-bold">
<Link
className="homepage-headling-link"
to="/biganimal/latest/using_cluster/06_demonstration_oracle_compatibility/"
to="/epas/latest/"
>
Demonstration of Oracle SQL <br />
compatibility in EDB BigAnimal
EDB Postgres Advanced Server <br />
Version 15
</Link>
</h3>
<p>
EDB BigAnimal lets you run Oracle SQL queries in the cloud via
EDB Postgres Advanced Server. Watch the video, or load up psql
and follow along.
EDB Postgres Advanced Server 15.2.0, which is built on
open-source PostgreSQL 15.2, includes compatibility with
Oracle and enhanced security, administration, and performance
features.
</p>
<div className="d-flex align-items-center">
<p>
<Link
className="btn btn-info btn-sm"
to="/biganimal/latest/using_cluster/06_demonstration_oracle_compatibility/"
className="btn-sm ml-2"
to="/epas/latest/epas_rel_notes/epas15_2_0_rel_notes/"
>
Watch demo
</Link>
</p>
<p>
<Link className="btn-sm ml-2" to="/biganimal/latest/">
Find out more &rarr;
</Link>
</p>
Expand All @@ -87,7 +85,7 @@ const Page = () => (
<div className="mb-2">
<div className="new-thing-header" aria-roledescription="badge">
<span className="badge-text font-weight-bold">
Interactive Demo
What's new
</span>
</div>
</div>
Expand All @@ -96,31 +94,19 @@ const Page = () => (
<h3 className="card-title mb-2 font-weight-bold">
<Link
className="homepage-headling-link"
to="/postgres_for_kubernetes/latest/interactive_demo/"
to="/pg_extensions/"
>
Install, Configure and Deploy PostgreSQL <br />
with Kubernetes
New Postgres extensions <br />
and tools
</Link>
</h3>
<p>
Want to see what it takes to get the EDB Postgres for
Kubernetes Operator up and running? Try in the browser now, no
downloads required.
• EDB Advanced Storage Pack <br />
• EDB Postgres Tuner <br />• EDB LDAP Sync
</p>
<div className="d-flex align-items-center">
<p>
<Link
className="btn btn-info btn-sm"
to="/postgres_for_kubernetes/latest/interactive_demo/"
>
Try it now
</Link>
</p>
<p>
<Link
className="btn-sm ml-2"
to="/postgres_for_kubernetes/latest/"
>
<Link className="btn-sm ml-2" to="/pg_extensions/">
Find out more &rarr;
</Link>
</p>
Expand Down

2 comments on commit b042d3e

@github-actions
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎉 Published on https://edb-docs-staging.netlify.app as production
🚀 Deployed on https://63f7dafe9ac3901bf2c8441d--edb-docs-staging.netlify.app

@github-actions
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎉 Published on https://edb-docs.netlify.app as production
🚀 Deployed on https://63f7df4d5ccd6f007c261d7e--edb-docs.netlify.app

Please sign in to comment.