Skip to content

Commit

Permalink
Merge pull request #3761 from EnterpriseDB/release/2023-03-03
Browse files Browse the repository at this point in the history
Release: 2023-03-03
  • Loading branch information
drothery-edb authored Mar 3, 2023
2 parents f1e7b98 + 4dad6b6 commit 4fba229
Show file tree
Hide file tree
Showing 11 changed files with 59 additions and 22 deletions.
4 changes: 2 additions & 2 deletions advocacy_docs/pg_extensions/advanced_storage_pack/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ navigation:
- configuring
---

EDB Advanced Storage Pack provides advanced storage options for PostgreSQL databases in the form of table access method (TAM) extensions. These storage options can enhance the performance and reliability of databases without requiring application changes.
EDB Advanced Storage Pack provides advanced storage options for Postgres databases in the form of table access method (TAM) extensions. These storage options can enhance the performance and reliability of databases without requiring application changes.

For tables whose access patterns you know, you might prefer a targeted TAM that makes different tradeoffs. For instance, if a table has a specific usage pattern, you might consider using a specialized TAM that is designed to enhance that usage pattern.

Expand All @@ -22,4 +22,4 @@ See [Autocluster example](using/#autocluster-example) for an example use case.

The Refdata TAM is optimized for mostly static data, which contains an occasional INSERT and very few DELETE and UPDATE commands. For database schemas that use foreign keys to reference data, this TAM can provide performance gains of 5-10% and increased scalability. Whenever anyone modifies a Refdata table, the modifying transaction takes a table-level ExclusiveLock, blocking out concurrent modifications by any other session as well as modifications to tables that reference the table.

See [Refdata exampe](using/#refdata-example) for an example use case.
See [Refdata exampe](using/#refdata-example) for an example use case.
4 changes: 4 additions & 0 deletions product_docs/docs/tpa/23/INSTALL.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -109,6 +109,10 @@ privileges. You may use any other means to run the commands as root.
Next, run `tpaexec setup` to create an isolated Python environment and
install the correct versions of all required modules.

!!! Note
On Ubuntu versions prior to 20.04, please use `sudo -H tpaexec setup`
(to avoid subsequent permission errors during `tpaexec configure`)

```bash
$ sudo /opt/EDB/TPA/bin/tpaexec setup
```
Expand Down
10 changes: 8 additions & 2 deletions product_docs/docs/tpa/23/architecture-BDR-Always-ON.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -4,9 +4,15 @@ originalFilePath: architecture-BDR-Always-ON.md

---

BDR in an Always-ON configuration, intended for use in production.
EDB Postgres Distributed 4 or below in an Always-ON configuration,
suitable for use in test and production.

In BDR-Always-ON architecture we have four variants, which can be
This architecture requires a subscription to the legacy 2ndQuadrant
repositories, and some options require a subscription to EDB Repos 1.0.
See [How TPA uses 2ndQuadrant and EDB repositories](reference/2q_and_edb_repositories)
for more detail on this topic.

The BDR-Always-ON architecture has four variants, which can be
selected with the `--layout` configure option:

1. bronze: 2Γ—bdr+primary, bdr+witness, barman, 2Γ—harp-proxy
Expand Down
14 changes: 13 additions & 1 deletion product_docs/docs/tpa/23/architecture-M1.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,19 @@ originalFilePath: architecture-M1.md

A Postgres cluster with a primary and a streaming replica, one Barman
server, and any number of additional replicas cascaded from the first
one.
one. This architecture is suitable for testing, demonstrating and
learning. We plan to release a production primary/standby architecture
for TPA in the near future.

In default configuration this architecture uses open source software
only. To use subscription-only EDB software with this architecture
requires credentials for EDB Repos 1.0. If you choose EDB Advanced
Server (EPAS) you will also require credentials for the legacy
2ndQuadrant repos.
See [How TPA uses 2ndQuadrant and EDB repositories](reference/2q_and_edb_repositories)
for more detail on this topic.

## Default layout

By default, the primary has one read-only replica attached in the same
location; the replica, in turn, has one cascaded replica attached in a
Expand Down
6 changes: 4 additions & 2 deletions product_docs/docs/tpa/23/architecture-PGD-Always-ON.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -4,9 +4,11 @@ originalFilePath: architecture-PGD-Always-ON.md

---

EDB Postgres Distributed in an Always-ON configuration, intended for use in production.
EDB Postgres Distributed 5 in an Always-ON configuration,
suitable for use in test and production.

This architecture is meant for use with PGD (BDR) version 5 only.
This architecture is valid for use with PGD version 5 only and requires
a subscription to [EDB Repos 2.0](reference/2q_and_edb_repositories).

## Cluster configuration

Expand Down
3 changes: 2 additions & 1 deletion product_docs/docs/tpa/23/misc-troubleshooting.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,8 @@ To create a new virtual environment (assuming tpaexec was installed into the def
[tpa]$ sudo /opt/EDB/TPA/bin/tpaexec setup
```

\###Strange AWS errors regarding credentials
### Strange AWS errors regarding credentials

If the time & date of the TPA server isn't correct, you can get AWS errors similar to this during provisioning:

```
Expand Down
23 changes: 15 additions & 8 deletions product_docs/docs/tpa/23/reference/2q_and_edb_repositories.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,10 @@ ensure that you have a valid subscription for all the sources used and
that you have [exported the token](#authenticating-with-package-sources)
before running `tpaexec deploy` or the operation will fail.

!!! Note
EDB is in the process of publishing all software through Repos 2.0,
and will eventually remove the older repositories.

## Authenticating with package sources

To use [EDB Repos 2.0](https://www.enterprisedb.com/repos/) you must
Expand All @@ -58,15 +62,18 @@ register for access at

## How sources are selected by default

For M1 and BDR-Always-ON architectures, the default source is
2ndQuadrant and the necessary repositories will be added from this
source. For software that is not available from this source (e.g EDB
Advanced Server), repositories will be selected from EDB Repos 1.0.

If the PGD-Always-ON architecture is selected, repositories will be
selected from EDB Repos 2.0 and all software will be sourced
from these repositories.

For M1 and BDR-Always-ON architectures, the default source is
2ndQuadrant, and the necessary repositories will be added from this
source. In addition, the PGDG repositories will be used for community
packages such as PostgreSQL and etcd as required.
If EDB software not available in the 2ndQuadrant repos is required
(e.g. EDB Advanced Server), repositories will be selected from EDB Repos
1.0.

## Specifying EDB 2.0 repositories

To specify the complete list of repositories from EDB Repos 2.0 to
Expand All @@ -80,8 +87,8 @@ cluster_vars:
- postgres_distributed
```

This example will install enterprise subscription repository as well as
postgres_distributed giving access to EPAS and BDR4+ products.
This example will configure the `enterprise` and `postgres_distributed`
repositories, giving access to EPAS and PGD5 products.
On Debian and Ubuntu systems, it will use the APT repository, and on
RedHat systems, it will use the YUM repository.

Expand All @@ -106,7 +113,7 @@ On Debian and Ubuntu systems, it will use the APT repository, and on
RedHat systems, it will use the YUM repository.

The `dl/default/release` repository is always installed by default,
unless you
unless you

- explicitly set `tpa_2q_repositories: []`, or
- have at least one entry in `edb_repositories`.
Expand Down
2 changes: 1 addition & 1 deletion product_docs/docs/tpa/23/reference/barman.mdx
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
title: 'Barman'
title: Barman
originalFilePath: barman.md

---
Expand Down
2 changes: 1 addition & 1 deletion product_docs/docs/tpa/23/reference/bdr.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ Access to PGD/BDR packages is through EDB's package repositories only.
You must have a valid EDB subscription token to download the packages.

This documentation touches on several aspects of BDR configuration, but
we refer you to the [PGD documentation](/pgd/latest) for an authoritative
we refer you to the [PGD documentation](https://enterprisedb.com/docs/pgd/latest/) for an authoritative
description of the details.

## Introduction
Expand Down
8 changes: 4 additions & 4 deletions product_docs/docs/tpa/23/reference/edb_repositories.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -4,10 +4,10 @@ originalFilePath: edb_repositories.md

---

This page explains how to configure EDB Repos 2.0 package repositories
This page explains how to configure EDB Repos 2.0 package repositories
on any system.

For more details on the EDB and 2ndQuadrant package sources used by
For more details on the EDB and 2ndQuadrant package sources used by
TPA see [this page](2q_and_edb_repositories).

To specify the complete list of repositories from EDB Repos 2.0 to
Expand All @@ -21,8 +21,8 @@ cluster_vars:
- postgres_distributed
```
This example will install enterprise subscription repository as well as
postgres_distributed giving access to EPAS and BDR4+ products.
This example will install the enterprise subscription repository as well
as postgres_distributed giving access to EPAS and PGD5 products.
On Debian and Ubuntu systems, it will use the APT repository, and on
RedHat systems, it will use the YUM repository.
Expand Down
5 changes: 5 additions & 0 deletions product_docs/docs/tpa/23/reference/git-credentials.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,11 @@ disk on the target instance:
`export TPA_GIT_CREDENTIALS=username:token` in your environment
before running `tpaexec deploy`.

!!! Note
When deploying to Docker on macOS, you should use only `https://`
repository URLs because Docker containers cannot be accessed by ssh
from the host in this environment.

## SSH key authentication

If you are cloning an SSH repository and have an SSH keypair
Expand Down

2 comments on commit 4fba229

@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://64026d8b2bd72c26e2c3e131--edb-docs.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.

Please sign in to comment.