Merge pull request #3826 from EnterpriseDB/release/2023-03-20

Release: 2023-03-20
EnterpriseDB · Mar 20, 2023 · ff0e6db · ff0e6db · github-actions · Mar 20, 2023
2 parents 86b9940 + 22fba86
commit ff0e6db
Show file tree

Hide file tree

Showing 91 changed files with 502 additions and 137 deletions.
diff --git a/...docs/epas/15/epas_compat_spl/05_control_structures/09_pragma_exception_init.mdx b/...docs/epas/15/epas_compat_spl/05_control_structures/09_pragma_exception_init.mdx
@@ -40,6 +40,7 @@ CREATE OR REPLACE PACKAGE BODY ar AS
         RAISE overdrawn;
       END IF;
   END;
+END;
 ```
 
 The following procedure calls the `check_balance` procedure. If `p_amount` is greater than `p_balance`, `check_balance` raises an exception. The `purchase` procedure catches the `ar.overdrawn` exception.
@@ -48,7 +49,7 @@ The following procedure calls the `check_balance` procedure. If `p_amount` is gr
 CREATE PROCEDURE purchase(customerID int, amount NUMERIC)
 AS
   BEGIN
-     ar.check_ balance(getcustomerbalance(customerid), amount);
+     ar.check_balance(getcustomerbalance(customerid), amount);
        record_purchase(customerid, amount);
   EXCEPTION
      WHEN ar.overdrawn THEN
@@ -77,7 +78,7 @@ This example uses a predefined exception. The code creates a more meaningful nam
 
 ```sql
 CREATE OR REPLACE PACKAGE ar AS
-  overdrawn EXCEPTION;
+  unknown_customer EXCEPTION;
   PRAGMA EXCEPTION_INIT (unknown_customer, no_data_found);
   PROCEDURE check_balance(p_customer_id NUMBER);
 END;
@@ -94,4 +95,5 @@ CREATE OR REPLACE PACKAGE BODY ar AS
      DBMS_OUTPUT.PUT_LINE('invalid customer id');
      RAISE;
    END;
+END;
 ```
diff --git a/..._rel_notes/08_jdbc_42.3.3.1_rel_notes.mdx → ..._rel_notes/08_jdbc_42.3.3.1_rel_notes.mdx b/..._rel_notes/08_jdbc_42.3.3.1_rel_notes.mdx → ..._rel_notes/08_jdbc_42.3.3.1_rel_notes.mdx
diff --git a/..._rel_notes/09_jdbc_42.3.2.1_rel_notes.mdx → ..._rel_notes/09_jdbc_42.3.2.1_rel_notes.mdx b/..._rel_notes/09_jdbc_42.3.2.1_rel_notes.mdx → ..._rel_notes/09_jdbc_42.3.2.1_rel_notes.mdx
diff --git a/...rel_notes/10_jdbc_42.2.24.1_rel_notes.mdx → ...rel_notes/10_jdbc_42.2.24.1_rel_notes.mdx b/...rel_notes/10_jdbc_42.2.24.1_rel_notes.mdx → ...rel_notes/10_jdbc_42.2.24.1_rel_notes.mdx
diff --git a/...rel_notes/12_jdbc_42.2.19.1_rel_notes.mdx → ...rel_notes/12_jdbc_42.2.19.1_rel_notes.mdx b/...rel_notes/12_jdbc_42.2.19.1_rel_notes.mdx → ...rel_notes/12_jdbc_42.2.19.1_rel_notes.mdx
diff --git a/...rel_notes/14_jdbc_42.2.12.3_rel_notes.mdx → ...rel_notes/14_jdbc_42.2.12.3_rel_notes.mdx b/...rel_notes/14_jdbc_42.2.12.3_rel_notes.mdx → ...rel_notes/14_jdbc_42.2.12.3_rel_notes.mdx
diff --git a/..._rel_notes/16_jdbc_42.2.9.1_rel_notes.mdx → ..._rel_notes/16_jdbc_42.2.9.1_rel_notes.mdx b/..._rel_notes/16_jdbc_42.2.9.1_rel_notes.mdx → ..._rel_notes/16_jdbc_42.2.9.1_rel_notes.mdx
diff --git a/..._rel_notes/18_jdbc_42.2.8.1_rel_notes.mdx → ..._rel_notes/18_jdbc_42.2.8.1_rel_notes.mdx b/..._rel_notes/18_jdbc_42.2.8.1_rel_notes.mdx → ..._rel_notes/18_jdbc_42.2.8.1_rel_notes.mdx
diff --git a/...ctor/42.5.1.2/01_jdbc_rel_notes/index.mdx → ...ctor/42.5.4.1/01_jdbc_rel_notes/index.mdx b/...ctor/42.5.1.2/01_jdbc_rel_notes/index.mdx → ...ctor/42.5.4.1/01_jdbc_rel_notes/index.mdx
@@ -1,6 +1,7 @@
 ---
 title: "Release notes"
 navigation:
+- jdbc_42.5.4.1_rel_notes
 - jdbc_42.5.1.2_rel_notes
 - jdbc_42.5.1.1_rel_notes
 - jdbc_42.5.0.1_rel_notes
@@ -12,6 +13,7 @@ These release notes describe what's new in each release. When a minor or patch r
 
 | Version                                  | Release Date | 
 | ---------------------------------------- | ------------ | 
+| [42.5.4.1](jdbc_42.5.4.1_rel_notes)      | 2023 Mar 16  |
 | [42.5.1.2](jdbc_42.5.1.2_rel_notes)      | 2023 Feb 14  |
 | [42.5.1.1](jdbc_42.5.1.1_rel_notes)      | 2022 Dec 9   |
 | [42.5.0.1](jdbc_42.5.0.1_rel_notes)      | 2022 Sep 1   |

diff --git a/...dbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx → ...dbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx b/...dbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx → ...dbc_rel_notes/jdbc_42.5.0.1_rel_notes.mdx
diff --git a/...dbc_rel_notes/jdbc_42.5.1.1_rel_notes.mdx → ...dbc_rel_notes/jdbc_42.5.1.1_rel_notes.mdx b/...dbc_rel_notes/jdbc_42.5.1.1_rel_notes.mdx → ...dbc_rel_notes/jdbc_42.5.1.1_rel_notes.mdx
diff --git a/...dbc_rel_notes/jdbc_42.5.1.2_rel_notes.mdx → ...dbc_rel_notes/jdbc_42.5.1.2_rel_notes.mdx b/...dbc_rel_notes/jdbc_42.5.1.2_rel_notes.mdx → ...dbc_rel_notes/jdbc_42.5.1.2_rel_notes.mdx
diff --git a/...docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/jdbc_42.5.4.1_rel_notes.mdx b/...docs/docs/jdbc_connector/42.5.4.1/01_jdbc_rel_notes/jdbc_42.5.4.1_rel_notes.mdx
@@ -0,0 +1,23 @@
+---
+title: "Version 42.5.4.1"
+
+---
+
+The EDB JDBC connector provides connectivity between a Java application and an EDB Postgres Advanced Server database.
+
+New features, enhancements, bug fixes, and other changes in the EDB JDBC Connector 42.5.4.1 include:
+
+|      Type      |                                                                                   Description                                                                                    |
+| -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Upstream Merge | Merged with the upstream community driver version 42.5.4. See the community [JDBC documentation](https://jdbc.postgresql.org/changelogs/2023-02-16-42.5.4-release/) for details. |
+| Bug fix        | Fixed an issue in which there was missing information in the MANIFEST.MF file. [Support Ticket #89609]                                                                           |
+
+
+
+
+
+
+
+
+
+
diff --git a/...tor/42.5.1.2/02_requirements_overview.mdx → ...tor/42.5.4.1/02_requirements_overview.mdx b/...tor/42.5.1.2/02_requirements_overview.mdx → ...tor/42.5.4.1/02_requirements_overview.mdx
@@ -15,6 +15,7 @@ This table lists the latest JDBC Connector versions and their supported correspo
 
 |                       JDBC Connector                       | EPAS 15 | EPAS 14 | EPAS 13 | EPAS 12 | EPAS 11 |
 | ---------------------------------------------------------- | ------- | ------- | ------- | ------- | ------- |
+| [42.5.4.1](01_jdbc_rel_notes/jdbc_42.5.4.1_rel_notes)      | Y       | Y       | Y       | Y       | Y       |
 | [42.5.1.2](01_jdbc_rel_notes/jdbc_42.5.1.2_rel_notes)      | Y       | Y       | Y       | Y       | Y       |
 | [42.5.1.1](01_jdbc_rel_notes/jdbc_42.5.1.1_rel_notes)      | N       | Y       | Y       | Y       | Y       |
 | [42.5.0.1](01_jdbc_rel_notes/jdbc_42.5.0.1_rel_notes)      | N       | Y       | Y       | Y       | Y       |

diff --git a/...vanced_server_jdbc_connector_overview.mdx → ...vanced_server_jdbc_connector_overview.mdx b/...vanced_server_jdbc_connector_overview.mdx → ...vanced_server_jdbc_connector_overview.mdx
diff --git a/...ng_the_advanced_server_jdbc_connector.mdx → ...ng_the_advanced_server_jdbc_connector.mdx b/...ng_the_advanced_server_jdbc_connector.mdx → ...ng_the_advanced_server_jdbc_connector.mdx
diff --git a/...e/01_additional_connection_properties.mdx → ...e/01_additional_connection_properties.mdx b/...e/01_additional_connection_properties.mdx → ...e/01_additional_connection_properties.mdx
diff --git a/...ynchronous_secondary_database_servers.mdx → ...ynchronous_secondary_database_servers.mdx b/...ynchronous_secondary_database_servers.mdx → ...ynchronous_secondary_database_servers.mdx
diff --git a/...s/02_connecting_to_the_database/index.mdx → ...s/02_connecting_to_the_database/index.mdx b/...s/02_connecting_to_the_database/index.mdx → ...s/02_connecting_to_the_database/index.mdx
diff --git a/..._statements_through_statement_objects.mdx → ..._statements_through_statement_objects.mdx b/..._statements_through_statement_objects.mdx → ..._statements_through_statement_objects.mdx
diff --git a/...eving_results_from_a_resultset_object.mdx → ...eving_results_from_a_resultset_object.mdx b/...eving_results_from_a_resultset_object.mdx → ...eving_results_from_a_resultset_object.mdx
diff --git a/...ava_applications/05_freeing_resources.mdx → ...ava_applications/05_freeing_resources.mdx b/...ava_applications/05_freeing_resources.mdx → ...ava_applications/05_freeing_resources.mdx
diff --git a/..._java_applications/06_handling_errors.mdx → ..._java_applications/06_handling_errors.mdx b/..._java_applications/06_handling_errors.mdx → ..._java_applications/06_handling_errors.mdx
diff --git a/...onnector_with_java_applications/index.mdx → ...onnector_with_java_applications/index.mdx b/...onnector_with_java_applications/index.mdx → ...onnector_with_java_applications/index.mdx
diff --git a/.../42.5.1.2/05a_using_advanced_queueing.mdx → .../42.5.4.1/05a_using_advanced_queueing.mdx b/.../42.5.1.2/05a_using_advanced_queueing.mdx → .../42.5.4.1/05a_using_advanced_queueing.mdx
diff --git a/...ing_sql_commands_with_executeUpdate().mdx → ...ing_sql_commands_with_executeUpdate().mdx b/...ing_sql_commands_with_executeUpdate().mdx → ...ing_sql_commands_with_executeUpdate().mdx
diff --git a/...graphical_interface_to_a_java_program.mdx → ...graphical_interface_to_a_java_program.mdx b/...graphical_interface_to_a_java_program.mdx → ...graphical_interface_to_a_java_program.mdx
diff --git a/...ing_client-side_resource_requirements.mdx → ...ing_client-side_resource_requirements.mdx b/...ing_client-side_resource_requirements.mdx → ...ing_client-side_resource_requirements.mdx
diff --git a/...eparedstatements_to_send_sql_commands.mdx → ...eparedstatements_to_send_sql_commands.mdx b/...eparedstatements_to_send_sql_commands.mdx → ...eparedstatements_to_send_sql_commands.mdx
diff --git a/...nality/03_executing_stored_procedures.mdx → ...nality/03_executing_stored_procedures.mdx b/...nality/03_executing_stored_procedures.mdx → ...nality/03_executing_stored_procedures.mdx
diff --git a/...nality/04_using_ref_cursors_with_java.mdx → ...nality/04_using_ref_cursors_with_java.mdx b/...nality/04_using_ref_cursors_with_java.mdx → ...nality/04_using_ref_cursors_with_java.mdx
diff --git a/...onality/05_using_bytea_data_with_java.mdx → ...onality/05_using_bytea_data_with_java.mdx b/...onality/05_using_bytea_data_with_java.mdx → ...onality/05_using_bytea_data_with_java.mdx
diff --git a/...bject_types_and_collections_with_java.mdx → ...bject_types_and_collections_with_java.mdx b/...bject_types_and_collections_with_java.mdx → ...bject_types_and_collections_with_java.mdx
diff --git a/...fication_handling_with_noticelistener.mdx → ...fication_handling_with_noticelistener.mdx b/...fication_handling_with_noticelistener.mdx → ...fication_handling_with_noticelistener.mdx
diff --git a/...ed_jdbc_connector_functionality/index.mdx → ...ed_jdbc_connector_functionality/index.mdx b/...ed_jdbc_connector_functionality/index.mdx → ...ed_jdbc_connector_functionality/index.mdx
diff --git a/...1_using_ssl/01_configuring_the_server.mdx → ...1_using_ssl/01_configuring_the_server.mdx b/...1_using_ssl/01_configuring_the_server.mdx → ...1_using_ssl/01_configuring_the_server.mdx
diff --git a/...1_using_ssl/02_configuring_the_client.mdx → ...1_using_ssl/02_configuring_the_client.mdx b/...1_using_ssl/02_configuring_the_client.mdx → ...1_using_ssl/02_configuring_the_client.mdx
diff --git a/...sl/03_testing_the_ssl_jdbc_connection.mdx → ...sl/03_testing_the_ssl_jdbc_connection.mdx b/...sl/03_testing_the_ssl_jdbc_connection.mdx → ...sl/03_testing_the_ssl_jdbc_connection.mdx
diff --git a/...ate_authentication_without_a_password.mdx → ...ate_authentication_without_a_password.mdx b/...ate_authentication_without_a_password.mdx → ...ate_authentication_without_a_password.mdx
diff --git a/...ity_and_encryption/01_using_ssl/index.mdx → ...ity_and_encryption/01_using_ssl/index.mdx b/...ity_and_encryption/01_using_ssl/index.mdx → ...ity_and_encryption/01_using_ssl/index.mdx
diff --git a/...and_encryption/02_scram_compatibility.mdx → ...and_encryption/02_scram_compatibility.mdx b/...and_encryption/02_scram_compatibility.mdx → ...and_encryption/02_scram_compatibility.mdx
diff --git a/...pport_for_gssapi_encrypted_connection.mdx → ...pport_for_gssapi_encrypted_connection.mdx b/...pport_for_gssapi_encrypted_connection.mdx → ...pport_for_gssapi_encrypted_connection.mdx
diff --git a/....1.2/09_security_and_encryption/index.mdx → ....4.1/09_security_and_encryption/index.mdx b/....1.2/09_security_and_encryption/index.mdx → ....4.1/09_security_and_encryption/index.mdx
diff --git a/...dvanced_server_jdbc_connector_logging.mdx → ...dvanced_server_jdbc_connector_logging.mdx b/...dvanced_server_jdbc_connector_logging.mdx → ...dvanced_server_jdbc_connector_logging.mdx
diff --git a/...42.5.1.2/11_reference_jdbc_data_types.mdx → ...42.5.4.1/11_reference_jdbc_data_types.mdx b/...42.5.1.2/11_reference_jdbc_data_types.mdx → ...42.5.4.1/11_reference_jdbc_data_types.mdx
diff --git a/....2/images/core_classes_and_interfaces.png → ....1/images/core_classes_and_interfaces.png b/....2/images/core_classes_and_interfaces.png → ....1/images/core_classes_and_interfaces.png
diff --git a/...42.5.1.2/images/drivermanager_drivers.png → ...42.5.4.1/images/drivermanager_drivers.png b/...42.5.1.2/images/drivermanager_drivers.png → ...42.5.4.1/images/drivermanager_drivers.png
diff --git a/...5.1.2/images/jdbc_class_relationships.png → ...5.4.1/images/jdbc_class_relationships.png b/...5.1.2/images/jdbc_class_relationships.png → ...5.4.1/images/jdbc_class_relationships.png
diff --git a/...1.2/images/jdbc_installation_complete.png → ...4.1/images/jdbc_installation_complete.png b/...1.2/images/jdbc_installation_complete.png → ...4.1/images/jdbc_installation_complete.png
diff --git a/...5.1.2/images/jdbc_installation_dialog.png → ...5.4.1/images/jdbc_installation_dialog.png b/...5.1.2/images/jdbc_installation_dialog.png → ...5.4.1/images/jdbc_installation_dialog.png
diff --git a/...5.1.2/images/jdbc_installation_wizard.png → ...5.4.1/images/jdbc_installation_wizard.png b/...5.1.2/images/jdbc_installation_wizard.png → ...5.4.1/images/jdbc_installation_wizard.png
diff --git a/...ctor/42.5.1.2/images/ready_to_install.png → ...ctor/42.5.4.1/images/ready_to_install.png b/...ctor/42.5.1.2/images/ready_to_install.png → ...ctor/42.5.4.1/images/ready_to_install.png
diff --git a/...es/selecting_the_connectors_installer.png → ...es/selecting_the_connectors_installer.png b/...es/selecting_the_connectors_installer.png → ...es/selecting_the_connectors_installer.png
diff --git a/...1.2/images/starting_stackbuilder_plus.png → ...4.1/images/starting_stackbuilder_plus.png b/...1.2/images/starting_stackbuilder_plus.png → ...4.1/images/starting_stackbuilder_plus.png
diff --git a/...5.1.2/images/the_showemployees_window.png → ...5.4.1/images/the_showemployees_window.png b/...5.1.2/images/the_showemployees_window.png → ...5.4.1/images/the_showemployees_window.png
diff --git a/...cs/docs/jdbc_connector/42.5.1.2/index.mdx → ...cs/docs/jdbc_connector/42.5.4.1/index.mdx b/...cs/docs/jdbc_connector/42.5.1.2/index.mdx → ...cs/docs/jdbc_connector/42.5.4.1/index.mdx
diff --git a/...5.1.2/installing/configuring_for_java.mdx → ...5.4.1/installing/configuring_for_java.mdx b/...5.1.2/installing/configuring_for_java.mdx → ...5.4.1/installing/configuring_for_java.mdx
diff --git a/...c_connector/42.5.1.2/installing/index.mdx → ...c_connector/42.5.4.1/installing/index.mdx b/...c_connector/42.5.1.2/installing/index.mdx → ...c_connector/42.5.4.1/installing/index.mdx
diff --git a/....5.1.2/installing/linux_ppc64le/index.mdx → ....5.4.1/installing/linux_ppc64le/index.mdx b/....5.1.2/installing/linux_ppc64le/index.mdx → ....5.4.1/installing/linux_ppc64le/index.mdx
diff --git a/.../installing/linux_ppc64le/jdbc_rhel_8.mdx → .../installing/linux_ppc64le/jdbc_rhel_8.mdx b/.../installing/linux_ppc64le/jdbc_rhel_8.mdx → .../installing/linux_ppc64le/jdbc_rhel_8.mdx
diff --git a/...installing/linux_ppc64le/jdbc_sles_12.mdx → ...installing/linux_ppc64le/jdbc_sles_12.mdx b/...installing/linux_ppc64le/jdbc_sles_12.mdx → ...installing/linux_ppc64le/jdbc_sles_12.mdx
diff --git a/...installing/linux_ppc64le/jdbc_sles_15.mdx → ...installing/linux_ppc64le/jdbc_sles_15.mdx b/...installing/linux_ppc64le/jdbc_sles_15.mdx → ...installing/linux_ppc64le/jdbc_sles_15.mdx
diff --git a/...2.5.1.2/installing/linux_x86_64/index.mdx → ...2.5.4.1/installing/linux_x86_64/index.mdx b/...2.5.1.2/installing/linux_x86_64/index.mdx → ...2.5.4.1/installing/linux_x86_64/index.mdx
diff --git a/...installing/linux_x86_64/jdbc_centos_7.mdx → ...installing/linux_x86_64/jdbc_centos_7.mdx b/...installing/linux_x86_64/jdbc_centos_7.mdx → ...installing/linux_x86_64/jdbc_centos_7.mdx
diff --git a/...nstalling/linux_x86_64/jdbc_debian_10.mdx → ...nstalling/linux_x86_64/jdbc_debian_10.mdx b/...nstalling/linux_x86_64/jdbc_debian_10.mdx → ...nstalling/linux_x86_64/jdbc_debian_10.mdx
diff --git a/...nstalling/linux_x86_64/jdbc_debian_11.mdx → ...nstalling/linux_x86_64/jdbc_debian_11.mdx b/...nstalling/linux_x86_64/jdbc_debian_11.mdx → ...nstalling/linux_x86_64/jdbc_debian_11.mdx
diff --git a/...lling/linux_x86_64/jdbc_other_linux_8.mdx → ...lling/linux_x86_64/jdbc_other_linux_8.mdx b/...lling/linux_x86_64/jdbc_other_linux_8.mdx → ...lling/linux_x86_64/jdbc_other_linux_8.mdx
diff --git a/...2/installing/linux_x86_64/jdbc_rhel_7.mdx → ...1/installing/linux_x86_64/jdbc_rhel_7.mdx b/...2/installing/linux_x86_64/jdbc_rhel_7.mdx → ...1/installing/linux_x86_64/jdbc_rhel_7.mdx
diff --git a/...2/installing/linux_x86_64/jdbc_rhel_8.mdx → ...1/installing/linux_x86_64/jdbc_rhel_8.mdx b/...2/installing/linux_x86_64/jdbc_rhel_8.mdx → ...1/installing/linux_x86_64/jdbc_rhel_8.mdx
diff --git a/.../installing/linux_x86_64/jdbc_sles_12.mdx → .../installing/linux_x86_64/jdbc_sles_12.mdx b/.../installing/linux_x86_64/jdbc_sles_12.mdx → .../installing/linux_x86_64/jdbc_sles_12.mdx
diff --git a/.../installing/linux_x86_64/jdbc_sles_15.mdx → .../installing/linux_x86_64/jdbc_sles_15.mdx b/.../installing/linux_x86_64/jdbc_sles_15.mdx → .../installing/linux_x86_64/jdbc_sles_15.mdx
diff --git a/...nstalling/linux_x86_64/jdbc_ubuntu_18.mdx → ...nstalling/linux_x86_64/jdbc_ubuntu_18.mdx b/...nstalling/linux_x86_64/jdbc_ubuntu_18.mdx → ...nstalling/linux_x86_64/jdbc_ubuntu_18.mdx
diff --git a/...nstalling/linux_x86_64/jdbc_ubuntu_20.mdx → ...nstalling/linux_x86_64/jdbc_ubuntu_20.mdx b/...nstalling/linux_x86_64/jdbc_ubuntu_20.mdx → ...nstalling/linux_x86_64/jdbc_ubuntu_20.mdx
diff --git a/...nnector/42.5.1.2/installing/upgrading.mdx → ...nnector/42.5.4.1/installing/upgrading.mdx b/...nnector/42.5.1.2/installing/upgrading.mdx → ...nnector/42.5.4.1/installing/upgrading.mdx
diff --git a/...connector/42.5.1.2/installing/windows.mdx → ...connector/42.5.4.1/installing/windows.mdx b/...connector/42.5.1.2/installing/windows.mdx → ...connector/42.5.4.1/installing/windows.mdx
diff --git a/product_docs/docs/pgd/4/harp/08_harpctl.mdx b/product_docs/docs/pgd/4/harp/08_harpctl.mdx
@@ -177,8 +177,7 @@ mycluster true
 ### `harpctl get leader`
 
 Fetches node information for the current lead master stored in the DCS for the 
-specified location. If no location is passed, `harpctl` attempts to 
-derive it based on the location of the current node where it was executed.
+specified location. Use [`harpctl get locations`](#harpctl-get-locations) to list the defined locations.
 
 Example:
 
@@ -192,9 +191,8 @@ mycluster mynode true  primary bdr  dc1      false  30
 
 ### `harpctl get location`
 
-Fetches location information for the specified location. If no location is 
-passed, `harpctl` attempts to derive it based on the location of the 
-current node where it was executed.
+Fetches location information for the specified location. Use [`harpctl get locations`](#harpctl-get-locations)
+to list the defined locations.
 
 Example:
 

diff --git a/product_docs/docs/postgres_for_kubernetes/1/addons.mdx b/product_docs/docs/postgres_for_kubernetes/1/addons.mdx
@@ -19,7 +19,7 @@ annotation.
 
 ## External Backup Adapter
 
-The `external-backup-adapter` add-on provides a generic way to integrate
+The external backup adapter add-ons provide a generic way to integrate
 EDB Postgres for Kubernetes in a third-party tool for backups through
 customizable ways to identify via labels and/or annotations:
 
@@ -28,7 +28,18 @@ customizable ways to identify via labels and/or annotations:
 -   the Pod running the PostgreSQL instance that has been selected for the backup
     (a standby or, if not available, the primary)
 
-The add-on allows you to define the names of the annotations that will contain
+You can choose between two add-ons that only differ from each other for the way
+they allow you to configure the adapter for your backup system:
+
+-   `external-backup-adapter`: in case you want to customize the behavior at the
+    operator's configuration level via either a config map or a secret - and share
+    it with all the Postgres clusters that are managed by the operator's deployment
+    (see [the `external-backup-adapter` section below](#the-external-backup-adapter-add-on))
+-   `external-backup-adapter-cluster`: in case you want to customize the behavior
+    of the adapter at the Postgres cluster level, through a specific annotation
+    (see [the `external-backup-adapter-cluster` section below](#the-external-backup-adapter-cluster-add-on))
+
+Such add-ons allow you to define the names of the annotations that will contain
 the commands to be run before or after taking a backup in the pod selected by
 the operator.
 
@@ -38,8 +49,6 @@ to coordinate itself with a PostgreSQL cluster, or a set of them.
 Recovery simply relies on the operator to reconcile the cluster from an
 existing PVC group.
 
-The above behavior can be customized at the [operator's level configuration](operator_conf.md).
-
 !!! Important
     The External Backup Adapter is not a tool to perform backups. It simply
     provides a generic interface that any third-party backup tool in the Kubernetes
@@ -49,54 +58,29 @@ The above behavior can be customized at the [operator's level configuration](ope
 
 ### Customizing the adapter
 
-The adapter can be entirely configured at operator's level, as YAML content,
-via the `EXTERNAL_BACKUP_ADDON_CONFIGURATION` field in the operator's
-`ConfigMap`/`Secret`. For more information, please refer to the provided
-sample file or the example below:
+As mentioned above, the adapter can be configured in two ways, which then
+determines the actual `add-on` you need to use in your `Cluster` resource.
 
-```yaml
-apiVersion: v1
-kind: ConfigMap
-metadata:
-  name: postgresql-operator-controller-manager-config
-  namespace: postgresql-operator-system
-data:
-  # ...
-  EXTERNAL_BACKUP_ADDON_CONFIGURATION: |
-    electedResourcesDecorators:
-      - key: "app.example.com/elected"
-        metadataType: "label"
-        value: "true"
-    
-    excludedResourcesDecorators:
-      - key: "app.example.com/excluded"
-        metadataType: "label"
-        value: "true"
-      - key: "app.example.com/excluded-reason"
-        metadataType: "annotation"
-        value: "Not necessary for backup"
-    
-    backupInstanceDecorators:
-      - key: "app.example.com/hasHooks"
-        metadataType: "label"
-        value: "true"
+If you are planning to define the same behavior for all the Postgres `Cluster`
+resources managed by the operator, we recommend that you use the
+`external-backup-adapter` add-on, and configure the annotations/labels in the
+operator's configuration.
 
-    preBackupHookConfiguration:
-      container:
-        key: "app.example.com/pre-backup-container"
-      command:
-        key: "app.example.com/pre-backup-command"
-      onError:
-        key: "app.example.com/pre-backup-on-error"
-    
-    postBackupHookConfiguration:
-      container:
-        key: "app.example.com/post-backup-container"
-      command:
-        key: "app.example.com/post-backup-command"
-```
+If you are planning to have different behaviors for a subset of the Postgres
+`Cluster` resources that you have, we recommend that you use the
+`external-backup-adapter-cluster` add-on.
 
-Each section is explained below.
+Both add-ons share the same capabilities in terms of customization, which needs
+to be defined as a YAML object having the following keys:
+
+-   `electedResourcesDecorators`
+-   `excludedResourcesDecorators`
+-   `backupInstanceDecorators`
+-   `preBackupHookConfiguration`
+-   `postBackupHookConfiguration`
+
+Each section is explained below. Further down you'll find the instructions on
+how to customize each of the two add-ons, with some examples.
 
 #### The `electedResourcesDecorators` section
 
@@ -181,34 +165,163 @@ The following fields must be provided:
   is a fixed value and cannot be configured. Will be saved in the annotations. To
   decorate the pod with hooks refer to: `instanceWithHookDecorators`
 
+### The `external-backup-adapter` add-on
+
+The `external-backup-adapter` add-on can be entirely configured at operator's
+level via the `EXTERNAL_BACKUP_ADDON_CONFIGURATION` field in the operator's
+`ConfigMap`/`Secret`.
+
+For more information, please refer to the provided sample file at the end of
+this section, or the example below:
+
+```yaml
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: postgresql-operator-controller-manager-config
+  namespace: postgresql-operator-system
+data:
+  # ...
+  EXTERNAL_BACKUP_ADDON_CONFIGURATION: |-
+    electedResourcesDecorators:
+      - key: "app.example.com/elected"
+        metadataType: "label"
+        value: "true"
+    excludedResourcesDecorators:
+      - key: "app.example.com/excluded"
+        metadataType: "label"
+        value: "true"
+      - key: "app.example.com/excluded-reason"
+        metadataType: "annotation"
+        value: "Not necessary for backup"
+    backupInstanceDecorators:
+      - key: "app.example.com/hasHooks"
+        metadataType: "label"
+        value: "true"
+    preBackupHookConfiguration:
+      container:
+        key: "app.example.com/pre-backup-container"
+      command:
+        key: "app.example.com/pre-backup-command"
+      onError:
+        key: "app.example.com/pre-backup-on-error"
+    postBackupHookConfiguration:
+      container:
+        key: "app.example.com/post-backup-container"
+      command:
+        key: "app.example.com/post-backup-command"
+```
+
+The add-on can be activated by adding the following annotation to the `Cluster`
+resource:
+
+```yaml
+k8s.enterprisedb.io/addons: '["external-backup-adapter"]'
+```
+
+### The `external-backup-adapter-cluster` add-on
+
+The `external-backup-adapter-cluster` add-on must be configured in each
+`Cluster` resource you intend to use it through the
+`k8s.enterprisedb.io/externalBackupAdapterClusterConfig` annotation - which
+accepts the YAML object as content - as outlined in the following example:
+
+```yaml
+apiVersion: postgresql.k8s.enterprisedb.io/v1
+kind: Cluster
+metadata:
+  name: cluster-example
+  annotations:
+    "k8s.enterprisedb.io/addons": '["external-backup-adapter-cluster"]'
+    "k8s.enterprisedb.io/externalBackupAdapterClusterConfig": |-
+      electedResourcesDecorators:
+        - key: "app.example.com/elected"
+          metadataType: "label"
+          value: "true"
+      excludedResourcesDecorators:
+        - key: "app.example.com/excluded"
+          metadataType: "label"
+          value: "true"
+        - key: "app.example.com/excluded-reason"
+          metadataType: "annotation"
+          value: "Not necessary for backup"
+      backupInstanceDecorators:
+        - key: "app.example.com/hasHooks"
+          metadataType: "label"
+          value: "true"
+      preBackupHookConfiguration:
+        container:
+          key: "app.example.com/pre-backup-container"
+        command:
+          key: "app.example.com/pre-backup-command"
+        onError:
+          key: "app.example.com/pre-backup-on-error"
+      postBackupHookConfiguration:
+        container:
+          key: "app.example.com/post-backup-container"
+        command:
+          key: "app.example.com/post-backup-command"
+spec:
+  instances: 3
+  storage:
+    size: 1Gi
+```
+
+### About the fencing annotation
+
+If the configured external backup adapter backs up annotations, the fencing
+annotation will be set by the pre-backup hook and persist to the restored
+cluster. After restoring the cluster, you will need to manually remove the
+fencing annotation from the `Cluster` object to fix this.
+
+This can be done with the `cnp` plugin for kubectl:
+
+```shell
+kubectl cnp fencing off <cluster-name>
+```
+
+Or, if you don't have the `cnp` plugin, you can remove the fencing annotation
+manually with the following command:
+
+```shell
+kubectl annotate cluster <cluster-name> k8s.enterprisedb.io/fencedInstances-
+```
+
+Please refer to the [fencing documentation](fencing.md) for more information.
+
 ### Limitations
 
 As far as the backup part is concerned, currently, the EDB Postgres for
-Kubernetes integration with `external-backup-adapter` supports **cold backups**
-only. These are also referred to as **offline backups**. This means that the
-selected replica is temporarily fenced so that external-backup-adapter can take
-a physical snapshot of the PVC group - namely the `PGDATA` volume and, where
-available, the WAL volume.
+Kubernetes integration with `external-backup-adapter` and
+`external-backup-adapter-cluster` supports **cold backups** only. These are
+also referred to as **offline backups**. This means that the selected replica
+is temporarily fenced so that `external-backup-adapter` and
+`external-backup-adapter-cluster` can take a physical snapshot of the PVC group -
+namely the `PGDATA` volume and, where available, the WAL volume.
 
 In this short timeframe, the standby cannot accept read-only connections.
 If no standby is available - usually because we're in a single instance cluster -
 and the annotation `k8s.enterprisedb.io/snapshotAllowColdBackupOnPrimary` is
-set to true, `external-backup-adapter` will temporarily fence the primary,
-causing downtime in terms of read-write operations. This use case is normally
-left to development environments.
+set to true, `external-backup-adapter` and `external-backup-adapter-cluster`
+will temporarily fence the primary, causing downtime in terms of read-write
+operations. This use case is normally left to development environments.
 
 #### Full example of YAML file
 
-Here is a full example of YAML content to be placed in the
-`EXTERNAL_BACKUP_ADDON_CONFIGURATION` option as part of the
-the [operator's configuration process described above](#customizing-the-adapter).
+Here is a full example of YAML content to be placed in either:
+
+-   the `EXTERNAL_BACKUP_ADDON_CONFIGURATION` option as part of the
+    the operator's configuration process described above for the
+    `external-backup-adapter` add-on, or
+-   in the `k8s.enterprisedb.io/externalBackupAdapterClusterConfig` annotation
+    for the `external-backup-adapter-cluster` add-on
 
 !!! Hint
-    Copy the content below and paste it inside the `ConfigMap` or `Secret`
-    that you use to configure the operator, making sure you use the `|`
-    character that [YAML reserves for literals](https://yaml.org/spec/1.2.2/#812-literal-style),
-    as well as proper indentation. Use the comments to help you
-    customize the options for your tool.
+    Copy the content below and paste it inside the `ConfigMap` or `Secret` that
+    you use to configure the operator or the annotation in the `Cluster`, making
+    sure you use the `|` character that [YAML reserves for literals](https://yaml.org/spec/1.2.2/#812-literal-style),
+    as well as proper indentation. Use the comments to help you customize the
+    options for your tool.
 
 ```yaml
 # An array of labels and/or annotations that will be placed