EnterpriseDB · drothery-edb · Sep 7, 2023 · Aug 31, 2023 · Aug 31, 2023 · Aug 27, 2023
@@ -0,0 +1,5 @@
+# First pass basic codeowners file
+
+product_docs/docs/pgd/ @djw-m
+product_docs/docs/epas/ @nidhibhammar
+product_docs/docs/biganimal/ @drothery-edb
@@ -1,11 +1,9 @@
 ---
 title: Configuration options
 product: pglogical 2
-generatedBy: >-
-  /workspaces/docs/scripts/source/pglogical2.js - re-run to regenerate from
-  originalFilePath
+generatedBy: scripts/source/pglogical2.js - re-run to regenerate from originalFilePath
 originalFilePath: >-
-  https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L687-#L767
+  https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L691-#L771
 
 ---
 

@@ -1,11 +1,9 @@
 ---
 title: Conflicts
 product: pglogical 2
-generatedBy: >-
-  /workspaces/docs/scripts/source/pglogical2.js - re-run to regenerate from
-  originalFilePath
+generatedBy: scripts/source/pglogical2.js - re-run to regenerate from originalFilePath
 originalFilePath: >-
-  https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L673-#L685
+  https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L677-#L689
 
 ---
 

@@ -1,9 +1,7 @@
 ---
 title: pglogical 2
 product: pglogical 2
-generatedBy: >-
-  /workspaces/docs/scripts/source/pglogical2.js - re-run to regenerate from
-  originalFilePath
+generatedBy: scripts/source/pglogical2.js - re-run to regenerate from originalFilePath
 navigation:
   - index
   - release-notes

@@ -1,11 +1,9 @@
 ---
 title: Installation
 product: pglogical 2
-generatedBy: >-
-  /workspaces/docs/scripts/source/pglogical2.js - re-run to regenerate from
-  originalFilePath
+generatedBy: scripts/source/pglogical2.js - re-run to regenerate from originalFilePath
 originalFilePath: >-
-  https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L55-#L160
+  https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L55-#L164
 
 ---
 
@@ -36,6 +34,7 @@ If you don’t have PostgreSQL already:
     -   PostgreSQL 12: `yum install postgresql12-server postgresql12-contrib`
     -   PostgreSQL 13: `yum install postgresql13-server postgresql13-contrib`
     -   PostgreSQL 14: `yum install postgresql14-server postgresql14-contrib`
+    -   PostgreSQL 15: `yum install postgresql15-server postgresql15-contrib`
 
 Then install the “2ndQuadrant’s General Public” repository for your PostgreSQL
 version, by running the following instructions as root on the destination Linux server:
@@ -48,6 +47,7 @@ version, by running the following instructions as root on the destination Linux
 -   PostgreSQL 12: `curl https://techsupport.enterprisedb.com/api/repository/dl/default/release/12/rpm | bash`
 -   PostgreSQL 13: `curl https://techsupport.enterprisedb.com/api/repository/dl/default/release/13/rpm | bash`
 -   PostgreSQL 14: `curl https://techsupport.enterprisedb.com/api/repository/dl/default/release/14/rpm | bash`
+-   PostgreSQL 15: `curl https://techsupport.enterprisedb.com/api/repository/dl/default/release/15/rpm | bash`
 
 #### Installation
 
@@ -61,6 +61,7 @@ Once the repository is installed, you can proceed to pglogical for your PostgreS
 -   PostgreSQL 12: `yum install postgresql12-pglogical`
 -   PostgreSQL 13: `yum install postgresql13-pglogical`
 -   PostgreSQL 14: `yum install postgresql14-pglogical`
+-   PostgreSQL 15: `yum install postgresql15-pglogical`
 
 You may be prompted to accept the repository GPG key for package signing:
 
@@ -95,6 +96,7 @@ Once pre-requisites are complete, installing pglogical is simply a matter of exe
 -   PostgreSQL 12: `sudo apt-get install postgresql-12-pglogical`
 -   PostgreSQL 13: `sudo apt-get install postgresql-13-pglogical`
 -   PostgreSQL 14: `sudo apt-get install postgresql-14-pglogical`
+-   PostgreSQL 15: `sudo apt-get install postgresql-15-pglogical`
 
 ## From source code
 

@@ -1,11 +1,9 @@
 ---
 title: Limitations and restrictions
 product: pglogical 2
-generatedBy: >-
-  /workspaces/docs/scripts/source/pglogical2.js - re-run to regenerate from
-  originalFilePath
+generatedBy: scripts/source/pglogical2.js - re-run to regenerate from originalFilePath
 originalFilePath: >-
-  https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L769-#L938
+  https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L773-#L942
 
 ---
 

@@ -1,14 +1,34 @@
 ---
 title: Release Notes
 product: pglogical 2
-generatedBy: >-
-  /workspaces/docs/scripts/source/pglogical2.js - re-run to regenerate from
-  originalFilePath
+generatedBy: scripts/source/pglogical2.js - re-run to regenerate from originalFilePath
 originalFilePath: >-
-  https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L953-#L993
+  https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L957-#L1019
 
 ---
 
+## pglogical 2.4.3
+
+Version 2.4.3 is a maintenance release of pglogical 2.
+
+### Changes
+
+-   Apply data filtering on the correct tuple during initial synchronization.
+
+-   Restore the correct memory context while decoding a change.
+
+-   Drop database never completes in PostgreSQL 15.
+
+-   Don't replicate TRUNCATE as global message.
+
+## pglogical 2.4.2
+
+Version 2.4.2 is a maintenance release of pglogical 2.
+
+### Changes
+
+-   Add support for PostgreSQL 15.
+
 ## pglogical 2.4.1
 
 Version 2.4.1 is a maintenance release of pglogical 2.

@@ -1,9 +1,7 @@
 ---
 title: Requirements
 product: pglogical 2
-generatedBy: >-
-  /workspaces/docs/scripts/source/pglogical2.js - re-run to regenerate from
-  originalFilePath
+generatedBy: scripts/source/pglogical2.js - re-run to regenerate from originalFilePath
 originalFilePath: >-
   https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L36-#L53
 
@@ -24,4 +22,4 @@ be the same or weaker (more permissive) on the subscriber than the provider.
 Tables must have the same `PRIMARY KEY`s. It is not recommended to add additional
 `UNIQUE` constraints other than the `PRIMARY KEY` (see below).
 
-Some additional requirements are covered in [Limitations and Restrictions](limitations-and-restrictions.mdx).
+Some additional requirements are covered in [Limitations and Restrictions](limitations-and-restrictions).
@@ -1,11 +1,9 @@
 ---
 title: Synchronous Replication
 product: pglogical 2
-generatedBy: >-
-  /workspaces/docs/scripts/source/pglogical2.js - re-run to regenerate from
-  originalFilePath
+generatedBy: scripts/source/pglogical2.js - re-run to regenerate from originalFilePath
 originalFilePath: >-
-  https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L663-#L671
+  https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L667-#L675
 
 ---
 

@@ -1,11 +1,9 @@
 ---
 title: Usage
 product: pglogical 2
-generatedBy: >-
-  /workspaces/docs/scripts/source/pglogical2.js - re-run to regenerate from
-  originalFilePath
+generatedBy: scripts/source/pglogical2.js - re-run to regenerate from originalFilePath
 originalFilePath: >-
-  https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L162-#L661
+  https://github.com/2ndQuadrant/pglogical/blob/REL2_x_STABLE/docs/README.md?plain=1#L166-#L665
 
 ---
 

@@ -8,7 +8,7 @@ Released: 21 Aug 2023
 Updated: 30 Aug 2023
 
 !!! Important Upgrading
-Once you have upgraded to this version of EDB Postgres Advanced Server, you will need to run `edb_sqlpatch` on all your databases to complete the upgrade. This application will check that your databases system objects are up to date with this version. See the [EDB SQL Patch](/tools/edb_sqlpatch) documentation for more information on how to deploy this tool.
+After you upgrade to this version of EDB Postgres Advanced Server, you need to run `edb_sqlpatch` on all your databases to complete the upgrade. This application checks that your databases system objects are up to date with this version. See the [EDB SQL Patch](/tools/edb_sqlpatch) documentation for more information on how to deploy this tool.
 !!!
 
 !!! Note After applying patches

@@ -8,7 +8,7 @@ Released: 21 Aug 2023
 Updated: 30 Aug 2023
 
 !!! Important Upgrading
-Once you have upgraded to this version of EDB Postgres Advanced Server, you will need to run `edb_sqlpatch` on all your databases to complete the upgrade. This application will check that your databases system objects are up to date with this version. See the [EDB SQL Patch](/tools/edb_sqlpatch) documentation for more information on how to deploy this tool.
+After you upgrade to this version of EDB Postgres Advanced Server, you need to run `edb_sqlpatch` on all your databases to complete the upgrade. This application checks that your databases system objects are up to date with this version. See the [EDB SQL Patch](/tools/edb_sqlpatch) documentation for more information on how to deploy this tool.
 !!!
 
 !!! Note After applying patches

@@ -8,7 +8,7 @@ Released: 21 Aug 2023
 Updated: 30 Aug 2023
 
 !!! Important Upgrading
-Once you have upgraded to this version of EDB Postgres Advanced Server, you will need to run `edb_sqlpatch` on all your databases to complete the upgrade. This application will check that your databases system objects are up to date with this version. See the [EDB SQL Patch](/tools/edb_sqlpatch) documentation for more information on how to deploy this tool.
+After you upgrade to this version of EDB Postgres Advanced Server, you need to run `edb_sqlpatch` on all your databases to complete the upgrade. This application checks that your databases system objects are up to date with this version. See the [EDB SQL Patch](/tools/edb_sqlpatch) documentation for more information on how to deploy this tool.
 !!!
 
 !!! Note After applying patches

@@ -8,7 +8,7 @@ Released: 21 Aug 2023
 Updated: 30 Aug 2023
 
 !!! Important Upgrading
-Once you have upgraded to this version of EDB Postgres Advanced Server, you will need to run `edb_sqlpatch` on all your databases to complete the upgrade. This application will check that your databases system objects are up to date with this version. See the [EDB SQL Patch](/tools/edb_sqlpatch) documentation for more information on how to deploy this tool.
+After you upgrade to this version of EDB Postgres Advanced Server, you need to run `edb_sqlpatch` on all your databases to complete the upgrade. This application checks that your databases system objects are up to date with this version. See the [EDB SQL Patch](/tools/edb_sqlpatch) documentation for more information on how to deploy this tool.
 !!!
 
 !!! Note After applying patches

@@ -9,7 +9,7 @@ Released: 21 Aug 2023
 Updated: 30 Aug 2023
 
 !!! Important Upgrading
-Once you have upgraded to this version of EDB Postgres Advanced Server, you will need to run `edb_sqlpatch` on all your databases to complete the upgrade. This application will check that your databases system objects are up to date with this version. See the [EDB SQL Patch](/tools/edb_sqlpatch) documentation for more information on how to deploy this tool.
+After you upgrade to this version of EDB Postgres Advanced Server, you need to run `edb_sqlpatch` on all your databases to complete the upgrade. This application checks that your databases system objects are up to date with this version. See the [EDB SQL Patch](/tools/edb_sqlpatch) documentation for more information on how to deploy this tool.
 !!!
 
 !!! Note After applying patches

@@ -39,8 +39,9 @@ VARCHAR, VARCHAR2, NVARCHAR and NVARCHAR2
 
  If the string to assign is shorter than `n`, values of type `VARCHAR`, `VARCHAR2`, `NVARCHAR`, and `NVARCHAR2` store the shorter string without padding.
 
-   !!! Note
-      The trailing spaces are semantically significant in `VARCHAR` values.
+!!! Note
+The trailing spaces are semantically significant in `VARCHAR` values.
+!!!
 
  If you explicitly cast a value to a `VARCHAR` type, an over-length value is truncated to `n` characters without raising an error (as specified by the SQL standard).
 
@@ -55,4 +56,4 @@ VARCHAR, VARCHAR2, NVARCHAR and NVARCHAR2
 
  Thus, use of the `CLOB` type is limited by what can be done for `TEXT`, such as a maximum size of approximately 1 GB.
 
- For larger amounts of data, instead of using the `CLOB` data type, use the PostgreSQL *large objects* feature that relies on the `pg_largeobject` system catalog. For information on large objects, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/largeobjects.html).
+ For larger amounts of data, instead of using the `CLOB` data type, use the PostgreSQL *large objects* feature that relies on the `pg_largeobject` system catalog. For information on large objects, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/largeobjects.html).
@@ -5,13 +5,17 @@ title: "Certified and supported product versions"
 You can use the following database product versions with Replication Server:
 
 -   PostgreSQL versions 11, 12, 13, 14, and 15
--   Advanced Server versions 11, 12, 13, 14, and 15
+-   EDB Postgres Advanced Server versions 11, 12, 13, 14, and 15
 -   Oracle 11g Release 2 version 11.2.0.2.0 is explicitly certified. Newer minor versions in the 11.2 line are supported as well.
 -   Oracle 12c version 12.1.0.2.0 is explicitly certified. Newer minor versions in the 12.1 line are supported as well.
 -   Oracle 18c version 18.1.0.2.0 is explicitly certified. Newer minor versions in the 18.1 line are supported as well.
 -   Oracle 19c version 19.1.0.2.0 is explicitly certified. Newer minor versions in the 19.1 line are supported as well.
 -   SQL Server 2014 version 12.0.5000.0 is explicitly certified. Newer minor versions in the 12.0 line are supported as well.
 
+!!!Note
+   All PostgreSQL and EDB Postgres Advanced Server versions available as BigAnimal single-node and primary/standby high availability cluster types are also supported for SMR configurations. Consult the BigAnimal (EDB’s managed database cloud service) [documentation](/biganimal/latest) for more information about BigAnimal’s [supported cluster types](/biganimal/latest/overview/02_high_availability/) and [database version policy](/biganimal/latest/overview/05_database_version_policy/) for the versions of PostgreSQL and EDB Postgres Advanced Server available in BigAnimal.
+
+
 As of Replication Server 7.1.0:
 - SQL Server 2016 version 13.00.5026 is explicitly certified. Newer minor versions in the 13.0 line are supported as well.
 - SQL Server 2017 version 14.0.1000.169 is explicitly certified. Newer minor versions in the 14.0 line are supported as well.

@@ -85,11 +85,18 @@ The table shows whether a configuration property can be reloaded.
 
 This example reloads the configuration file.
 
-```shell
-$ java -jar edb-repcli.jar -reloadconf -repsvrfile ~/subsvr.prop
+!!! Note Note
+When you execute the reloadconf command, if any configuration options have been changed from their default values, the output includes the configuration option and its new value. 
 
+```shell
+java -jar edb-repcli.jar -reloadconf -repsvrfile subsvr.prop
+__OUTPUT__
 Reloading Subscription Server configuration file...
 Reloaded configuration options from ../etc/xdb_subserver.conf...
+The conf option 'snapshotParallelTableLoaderLimit' set to '1'
+The conf option 'skipCheckConst' set to 'false'
+The conf option 'snapshotParallelLoadCount' set to '1'
 
 Configuration was reloaded successfully.
 ```
+!!!
@@ -1,5 +1,6 @@
 ---
-title: "Controlling logging level, log file sizes, and rotation count"
+title: "Controlling logging level, log file sizes, rotation count, and locale"
+navTitle: "Controlling message logging"
 redirects:
 - /eprs/latest/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level
 ---
@@ -13,15 +14,15 @@ The following options control various aspects of message logging in the publicat
 
 See [Publication and subscription server startup failures](../../02_resolving_problems/02_where_to_look_for_errors/#pub_and_sub_startup_failures) and [Snapshot replication failures](../../02_resolving_problems/02_where_to_look_for_errors/#snapshot_replication_failures) for more information.
 
-`logging.level`
+## `logging.level`
 
 Set the `logging.level` option to control the severity of messages written to the publication server log file and the subscription server log file.
 
 `logging.level={OFF | SEVERE | WARNING | INFO | CONFIG | FINE | FINER | FINEST | ALL}`
 
 The default value is `WARNING`.
 
-`logging.file.size`
+## `logging.file.size`
 
 Set the `logging.file.size` option to control the maximum file size (in megabytes) of the publication server log file and the subscription server log file.
 
@@ -32,7 +33,7 @@ Set the `logging.file.size` option to control the maximum file size (in megabyte
 
 The default value is `50`, in megabytes.
 
-`logging.file.count`
+## `logging.file.count`
 
 Set the `logging.file.count` option to control the number of files in the log file rotation history of the publication server log file and the subscription server log file.
 
@@ -57,7 +58,21 @@ When log file rotation is enabled and the current, active log file (`pubserver.l
 -   Each remaining log file is renamed with the next greater integer suffix (`pubserver.log.m` is renamed to `pubserver.log.m+1`, with m varying from `0` to `n-2`).
 -   A new, active log file is created (`pubserver.log.0`).
 
-`mtk.logging.file.size`
+## `logging.default.locale` 
+
+Set the `logging.default.locale` option to use either the current system locale or English (en) for publication and subscription logs. 
+
+`logging.default.locale={system | en}`
+
+The default value is `system`.
+
+!!!Note
+This option is only applicable for publication and subscription logs and isn't supported for mtk.log.
+
+The RepCLI and RepConsole logs continue showing text in the default locale.
+!!!
+
+## `mtk.logging.file.size`
 
 !!! Note
     This option applies only to the publication server.
@@ -68,7 +83,7 @@ Set the `mtk.logging.file.size` option to control the maximum file size (in mega
 
 The default value is `50`, in megabytes.
 
-`mtk.logging.file.count`
+## `mtk.logging.file.count`
 
 !!! Note
     This option applies only to the publication server.
@@ -94,3 +109,5 @@ When the current, active log file (`mtk.log`) reaches the size specified by `mtk
 -   Each remaining log file with a suffix is renamed with the next greater integer suffix (`mtk.log.m` is renamed to `mtk.log.m+1`, with `m` varying from `1` to `n-1`).
 -   Log file `mtk.log` is renamed to `mtk.log.1`.
 -   A new, active log file is created (`mtk.log`).
+
+