Merge pull request #2148 from EnterpriseDB/release/2021-12-16

Release: 2021-12-16
EnterpriseDB · Dec 16, 2021 · 0ddf2a5 · 0ddf2a5
2 parents c652407 + 6ce0747
commit 0ddf2a5
Show file tree

Hide file tree

Showing 29 changed files with 498 additions and 730 deletions.
diff --git a/.github/workflows/deploy-develop.yml b/.github/workflows/deploy-develop.yml
@@ -78,6 +78,9 @@ jobs:
 
       - name: Netlify deploy
         run: |
+          # Pin netlify-cli due to install errors with 8.1.4, possibly related
+          # to <https://github.com/netlify/cli/issues/3840>. Try again when
+          # 8.1.5 is released.
           sudo npm install -g [email protected]
           netlify deploy --dir=public --prod
         env:

diff --git a/.github/workflows/deploy-main.yml b/.github/workflows/deploy-main.yml
@@ -81,6 +81,9 @@ jobs:
 
       - name: Netlify deploy
         run: |
+          # Pin netlify-cli due to install errors with 8.1.4, possibly related
+          # to <https://github.com/netlify/cli/issues/3840>. Try again when
+          # 8.1.5 is released.
           sudo npm install -g [email protected]
           netlify deploy --dir=public --prod
         env:

diff --git a/product_docs/docs/bdr/3.7/functions.mdx b/product_docs/docs/bdr/3.7/functions.mdx
@@ -56,9 +56,7 @@ Upon session initialization, this is set to the node id the client is
 connected to.  This allows an application to figure out what node it
 is connected to even behind a transparent proxy.
 
-It is also used in combination with CAMO, see the
-[Connection pools and proxies](camo#connection-pools-and-proxies)
-section.
+It is also used in combination with CAMO, see the [Connection pools and proxies](camo#connection-pools-and-proxies) section.
 
 ### bdr.last_committed_lsn
 

diff --git a/product_docs/docs/bdr/3.7/index.mdx b/product_docs/docs/bdr/3.7/index.mdx
@@ -114,5 +114,3 @@ Some features are only available on particular versions of Postgres server.
 
 Features that are currently available only with EDB Postgres Extended are
 expected to be available with EDB Postgres Advanced 14.
-
-This documentation is for the Enterprise Edition of BDR3.
diff --git a/product_docs/docs/bdr/3.7/known-issues.mdx b/product_docs/docs/bdr/3.7/known-issues.mdx
@@ -54,11 +54,3 @@ unique identifier.
 -   Decoding Worker feature does not work with CAMO/EAGER
 
 -   Decoding Worker works only with the default replication sets
-
--   When Decoding Worker is enabled in BDR node group and a BDR  node is shutdown
-    in fast mode immediately after starting it, the shutdown may not complete
-    because WAL sender does not exit. This happens because WAL sender waits for
-    WAL decoder to start and WAL decoder may never start since the node is
-    shutting down. The situation can be worked around by using an immediate
-    shutdown or waiting for WAL decoder to start. The WAL decoder process is
-    reported in `pglogical.workers` as well as `pg_stat_activity` catalogs.
diff --git a/product_docs/docs/bdr/3.7/release-notes.mdx b/product_docs/docs/bdr/3.7/release-notes.mdx
@@ -5,6 +5,84 @@ originalFilePath: release-notes.md
 
 ---
 
+## BDR 3.7.14
+
+This is a maintenance release for BDR 3.7 which includes minor
+improvements as well as fixes for issues identified in previous
+versions.
+
+Check also release notes for pglogical 3.7.14 for resolved issues
+which affect BDR as well.
+
+### Improvements
+
+-   Reduce frequency of CAMO partner connection attempts (EE)  
+    In case of a failure to connect to a CAMO partner to verify its
+    configuration and check the status of transactions, do not retry
+    immediately (leading to a fully busy pglogical manager process), but
+    throttle down repeated attempts to reconnect and checks to once per
+    minute.
+
+-   Ensure CAMO configuration is checked again after a reconnect (EE)
+
+-   Add dummy CAMO configuration catalogs and Raft support (BDR-1676)  
+    This is just to ease rolling upgrades from BDR 3.7 to 4.0.x on CAMO enabled
+    installations.
+
+-   Avoid unnecessary LCR segment reads (BDR-1426)  
+    We'll now only attempt to read new LCR segments when there are some available.
+    This should reduce I/O load when decoding worker is enabled.
+
+### Resolved Issues
+
+-   Switch from CAMO to Local Mode only after timeouts (EE, RT74892)  
+    Do not use the `catchup_interval` estimate when switching from CAMO
+    protected to Local Mode, as that could induce inadvertent switching
+    due to load spikes.  Use the estimate only when switching from Local
+    Mode back to CAMO protected (to prevent toggling forth and back due
+    to lag on the CAMO partner).
+
+-   Prevent duplicate values generated locally by galloc sequence in high
+    concurrency situations when the new chunk is used (RT76528)  
+    The galloc sequence could have temporarily produce duplicate value when
+    switching which chunk is used locally (but not across nodes) if there were
+    multiple sessions waiting for the new value. This is now fixed.
+
+-   Ensure that the group slot is moved forward when there is only one node in
+    the BDR group  
+    This prevents disk exhaustion due to WAL accumulation when the group is left
+    running with just single BDR node for prolonged period of time. This is not
+    recommended setup but the WAL accumulation was not intentional.
+
+-   Advance Raft protocol version when there is only one node in the BDR group  
+    Single node clusters would otherwise always stay on oldest support protocol 
+    until another node was added. This could limit available feature set on that
+    single node.
+
+### Other Changes
+
+-   Add CAMO configuration infrastructure needed for upgrade to BDR4 (BDR-1676)  
+    Add dummy CAMO configuration infrastructure bdr.camo_pairs table
+    and bdr.add/remove_camo_pair() functions to be able to upgrade a
+    CAMO enabled cluster to BDR4
+
+### Upgrades
+
+This release supports upgrading from following versions of BDR:
+
+-   3.7.9 and higher
+-   3.6.29
+
+## BDR 3.7.13.1
+
+This is a hotfix release for BDR 3.7.13.
+
+### Resolved Issues
+
+-   Fix potential FATAL error when using global DML locking with CAMO (BDR-1675, BDR-1655)
+
+-   Fix lag calculation for CAMO local mode delay (BDR-1681)
+
 ## BDR 3.7.13
 
 This is a maintenance release for BDR 3.7 which includes minor improvements

diff --git a/product_docs/docs/bdr/3.7/scaling.mdx b/product_docs/docs/bdr/3.7/scaling.mdx
@@ -4,8 +4,6 @@ originalFilePath: scaling.md
 
 ---
 
-AutoPartition provides automatic management of partitioned tables.
-
 AutoPartition allows tables to grow easily to large sizes by automatic
 partitioning management. This utilizes the additional features of BDR
 such as low-conflict locking of creating and dropping partitions.

diff --git a/product_docs/docs/bdr/3.7/twophase.mdx b/product_docs/docs/bdr/3.7/twophase.mdx
@@ -63,13 +63,4 @@ the second phase from the same node:
 
 ```sql
 COMMIT PREPARED 'some-global-id';
-<<<<<<< HEAD
-```
-
-=======
-
-```
-
->>>>>>> 28b38c3c5e30126e05b09e23103e68e4f874b621
-
 ```
diff --git a/product_docs/docs/biganimal/release/using_cluster/04_backup_and_restore.mdx b/product_docs/docs/biganimal/release/using_cluster/04_backup_and_restore.mdx
@@ -14,7 +14,7 @@ If a restore is necessary—for example, in case of an accidental `DROP TABLE` s
 
 Cluster restores aren't performed "in-place" on an existing cluster. Instead, a new cluster is created and initialized with data from the backup archive. Restores must replay the transaction logs between the most recent full database backup and the target restore point. Thus restore times (that is, RTO) are dependent on the write activity in the source cluster.
 
-You can restore backups into a new cluster in the same region.
+You can restore backups into a new cluster in any region supported by BigAnimal.
 
 #### Perform a cluster restore
 

diff --git a/product_docs/docs/efm/3/efm_quick_start/index.mdx b/product_docs/docs/efm/3/efm_quick_start/index.mdx
@@ -78,7 +78,7 @@ Provide values for the following properties on all cluster nodes:
 | `db.service.owner`      | The owner of the `data` directory (usually `postgres` or `enterprisedb`). Required only if the database is running as a service. |
 | `db.service.name`       | The name of the database service (used to restart the server). Required only if the database is running as a service.            |
 | `db.bin`                | The path to the `bin` directory (used for calls to `pg_ctl`).                                                                    |
-| `db.recovery.dir`       | The `data` directory in which EFM will find or create the `recovery.conf` file or the `standby.signal` file.                     |
+| `db.data.dir`           | The `data` directory in which EFM will find or create the `recovery.conf` file or the `standby.signal` file.                     |
 | `user.email`            | An email address at which to receive email notifications (notification text is also in the agent log file).                      |
 | `bind.address`          | The local address of the node and the port to use for EFM. The format is: `bind.address=1.2.3.4:7800`                            |
 | `is.witness`            | `true` on a witness node and `false` if it is a primary or standby.                                                              |

diff --git a/product_docs/docs/efm/4/efm_quick_start/index.mdx b/product_docs/docs/efm/4/efm_quick_start/index.mdx
@@ -75,7 +75,7 @@ Provide values for the following properties on all cluster nodes:
 | `db.service.owner`      | The owner of the `data` directory (usually `postgres` or `enterprisedb`). Required only if the database is running as a service. |
 | `db.service.name`       | The name of the database service (used to restart the server). Required only if the database is running as a service.            |
 | `db.bin`                | The path to the `bin` directory (used for calls to `pg_ctl`).                                                                    |
-| `db.recovery.dir`       | The `data` directory in which EFM will find or create the `recovery.conf` file or the `standby.signal` file.                     |
+| `db.data.dir`           | The `data` directory in which EFM will find or create the `recovery.conf` file or the `standby.signal` file.                     |
 | `user.email`            | An email address at which to receive email notifications (notification text is also in the agent log file).                      |
 | `bind.address`          | The local address of the node and the port to use for EFM. The format is: `bind.address=1.2.3.4:7800`                            |
 | `is.witness`            | `true` on a witness node and `false` if it is a primary or standby.                                                              |

diff --git a/product_docs/docs/epas/12/epas_inst_linux/02_supported_platforms.mdx b/product_docs/docs/epas/12/epas_inst_linux/02_supported_platforms.mdx
diff --git a/product_docs/docs/epas/12/epas_platform_support/index.mdx b/product_docs/docs/epas/12/epas_platform_support/index.mdx
@@ -0,0 +1,34 @@
+---
+title: "Supported Platforms"
+
+redirects:
+ - /epas/12/epas_inst_linux/02_supported_platforms
+ - /epas/12/epas_upgrade_guide/01_supported_platforms
+---
+
+EDB Postgres Advanced Server v12 installers support 64 bit Linux and Windows server platforms. The Advanced Server 12 RPM packages are supported on the following 64-bit Linux platforms:
+
+-   Red Hat Enterprise Linux (x86_64) 7.x and 8.x
+-   CentOS (x86_64) 7.x and 8.x
+-   OL (x86_64) 7.x and 8.x
+-   PPC64LE 8 running CentOS/RHEL 7.x
+
+The EDB Postgres Advanced Server 12 native packages are supported on the following 64-bit Linux platforms:
+
+-   Debian 9.x and 10.x
+-   Ubuntu 18.04 LTS
+
+Graphical installers are supported on the following 64-bit Windows platforms:
+
+-   Windows 2019
+-   Windows Server 2016
+-   Windows Server 2012 R2 Server 
+
+See [Platform Compatibility](https://www.enterprisedb.com/platform-compatibility) for additional information about supported platforms.
+
+**Limitations**
+
+The following limitations apply to EDB Postgres Advanced Server:
+
+-   The `data` directory of a production database should not be stored on an NFS file system.
+-   The LLVM JIT package is supported on RHEL or CentOS 7.x, 8.x, and SLES. LLVM JIT is not supported on PPC-LE 64 running RHEL or CentOS 7.x or 8.x.
diff --git a/product_docs/docs/epas/12/epas_rel_notes/06_epas12.9.13_rel_notes.mdx b/product_docs/docs/epas/12/epas_rel_notes/06_epas12.9.13_rel_notes.mdx
@@ -0,0 +1,16 @@
+---
+title: Version 12.9.13
+---
+
+EDB Postgres Advanced Server 12.9.13 includes the following bug fixes:
+
+| Type           | Description                                                                                                                                                                            | ID      | Category  |
+| -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | --------- |
+| Upstream Merge | Merged with community PostgreSQL 12.9. See the community [Release Notes](https://www.postgresql.org/docs/12/release-12-9.html) for details. |         |           |
+| Bug Fix        | Obey the AM meridian indicator correctly in `to_timestamp()`. [Support Ticket: #74035]                                                                                                 | DB-1497 |           |
+| Bug Fix        | Prevent possible crash after implicit rollback handling `Parse` protocol message. [Support Ticket: #72626]                                                                             | DB&#8209;1449 |           |
+| Bug Fix        | Fix possible server crash when the package is dropped from another session                                                                                                             | DB-1403 | SPL       |
+| Bug Fix        | Allow dynamic partition creation to non-owner insert queries. [Support Ticket: #1277884]                                                                                               | DB-1230 |           |
+| Bug Fix        | Populate the event type for missing node type.                                                                                                                                         | DB-1184 | edb_audit |
+| Bug Fix        | Fix server crash when the package is re-compiled in the same session. [Support Ticket: #1181417]                                                                                       | DB-1038 | SPL       |
+| Bug Fix        | Fix `edbldr` to dynamically look for `to_char()` and `to_date()` functions, so that it can be used for non-redwood mode. [Support Ticket: #1161302]                                    | DB-950  | edbldr    |
diff --git a/product_docs/docs/epas/12/epas_rel_notes/07_epas12.8.12_rel_notes.mdx b/product_docs/docs/epas/12/epas_rel_notes/07_epas12.8.12_rel_notes.mdx
@@ -0,0 +1,11 @@
+---
+title: Version 12.8.12
+---
+
+EDB Postgres Advanced Server 12.8.12 includes the following bug fixes:
+
+| Type           | Description                                                                                                                                                                                  | ID      | Category |
+| -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | -------- |
+| Upstream Merge | Merged with community PostgreSQL 12.8. See the community [Release Notes](https://www.postgresql.org/docs/12/release-12-8.html) for details.  |         |          |
+| Bug Fix        | Prevent possible crash after implicit rollback handling `Parse` message. [Support Ticket: #72626]                                                                                            | DB-1449 |          |
+| Bug Fix        | Allow use of the utility under non-redwood mode. [Support Ticket: #1161302]                                                                                                                  | DB-950  | edbldr   |
diff --git a/product_docs/docs/epas/12/epas_rel_notes/08_epas12.7.10_rel_notes.mdx b/product_docs/docs/epas/12/epas_rel_notes/08_epas12.7.10_rel_notes.mdx
@@ -0,0 +1,11 @@
+---
+title: Version 12.7.10
+---
+
+EDB Postgres Advanced Server 12.7.10 includes the following bug fixes:
+
+| Type    | Description                                                                                                                                       | ID      |
+| ------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | ------- |
+| Upstream Merge | Merged with community PostgreSQL 12.7. See the community [Release Notes](https://www.postgresql.org/docs/12/release-12-7.html) for details.  |         |          |
+| Bug Fix | Fix `pg_upgrade` to allow the system catalog composite type used in user tables.                                                                  | DB-1237 |
+| Bug Fix | Fix possible misbehavior when aborting an autonomous transaction and also fix interaction of autonomous transactions with `edb_stmt_level_tx=on`. | DB&#8209;1034 |
diff --git a/product_docs/docs/epas/12/epas_rel_notes/09_epas12.7_rel_notes.mdx b/product_docs/docs/epas/12/epas_rel_notes/09_epas12.7_rel_notes.mdx
@@ -0,0 +1,19 @@
+---
+title: Version 12.7
+---
+
+EDB Postgres Advanced Server 12.7 includes the following bug fixes:
+
+| Type           | Description                                                                                                                                                                        | ID      | Category       |
+| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | -------------- |
+| Upstream Merge | Merged with community PostgreSQL 12.7. See the community [Release Notes](https://www.postgresql.org/docs/12/release-12-7.html) for details.                                        |         |                |
+| Bug Fix        | Prevent some uses of `COMMIT` and `ROLLBACK` in stored procedures that were unsafe and could cause crashes. [Support Ticket: #1234722]                                             | DB-1183 |                |
+| Bug Fix        | Prevent `index_advisor` from interfering with materialized view creation. [Support Ticket: #1189859]                                                                               | DB-1154 |                |
+| Bug Fix        | Support password redaction in `edb_filter_log` with the extended protocol, specially used with connectors. [Support Ticket: #1234131]                                              | DB-1139 |                |
+| Bug Fix        | Correct `QUEUE` object handling in `EVENT TRIGGER`.                                                                                                                                | DB-1129 |                |
+| Bug Fix        | Correct `REDACTION COLUMN` object handling in `EVENT TRIGGER`.                                                                                                                     | DB-1129 |                |
+| Bug Fix        | Fix `pg_upgrade` to not fail when a custom configuration file directory is used. [Support Ticket: #1200560]                                                                        | DB&#8209;1084 |                |
+| Bug Fix        | Refrain from dropping trigger on parent table through partitioning dependency. [Support Ticket: #1187215]                                                                          | DB-1063 |                |
+| Bug Fix        | Free temporary memory to avoid PGA memory accumulation and exceeds errors. [Support Ticket: #1129386]                                                                              | DB-1061 | dblink_ora     |
+| Bug Fix        | Fix possible server crash with partition-wish join push-down code path.                                                                                                            | DB-1042 | edb_dblink_oci |
+| Bug Fix        | Fix incorrect error message in `edbldr`. [Support Ticket: #1104048]                                                                                                                | DB-826  |                |
Original file line number	Diff line number	Diff line change
Expand Up		@@ -114,5 +114,3 @@ Some features are only available on particular versions of Postgres server.

		Features that are currently available only with EDB Postgres Extended are
		expected to be available with EDB Postgres Advanced 14.

		This documentation is for the Enterprise Edition of BDR3.