Merge branch '17' into add-17.7.1-release-notes

Author: Andriciuc

.github/workflows/main.yml

@@ -43,9 +43,8 @@ jobs:
       - name: Deploy docs
         run: |
           mike deploy 17 -b publish -p
-          mike set-default 17 -b publish -p
-          mike retitle 17 "17 (LATEST)" -b publish -p
+          mike retitle 17 "17.6" -b publish -p
 
       
 
-          
+          

docs/migration.md

@@ -1,17 +1,16 @@
-# Migrate from PostgreSQL to Percona Distribution for PostgreSQL 
-
+# Migrate from PostgreSQL to Percona Distribution for PostgreSQL
 
 Percona Distribution for PostgreSQL includes the PostgreSQL database and additional extensions that have been selected to cover the needs of the enterprise and are guaranteed to work together. Percona Distribution for PostgreSQL is available as a software collection that is easy to deploy.
 
-We encourage users to migrate from their PostgreSQL deployments based on community binaries to Percona Distribution for PostgreSQL. This document provides the migration instructions. 
+We encourage users to migrate from their PostgreSQL deployments based on community binaries to Percona Distribution for PostgreSQL. This document provides the migration instructions.
 
-Depending on your business requirements, you may migrate to Percona Distribution for PostgreSQL either [on the same server](#migrate-on-the-same-server) or [onto a different server](#migrate-on-a-different-server). 
+Depending on your business requirements, you may migrate to Percona Distribution for PostgreSQL either [on the same server](#migrate-on-the-same-server) or [onto a different server](#migrate-on-a-different-server).
 
 ## Migrate on the same server
 
-=== ":material-debian: :material-debian: On Debian and Ubuntu Linux"
+=== ":material-debian: On Debian and Ubuntu Linux"
 
-     >To ensure that your data is safe during the migration, we recommend to make a backup of your data and all configuration files (such as `pg_hba.conf`, `postgresql.conf`, `postgresql.auto.conf`) using the tool of your choice. The backup process is out of scope of this document. You can use `pg_dumpall` or other tools of your choice. For more information, see the blog post [PostgreSQL Upgrade Using pg_dumpall](https://www.percona.com/blog/postgresql-upgrade-using-pg_dumpall/) by _Avinash Vallarapu_, _Fernando Laudares Camargos_, _Jobin Augustine_ and _Nickolay Ihalainen_.
+     >To ensure that your data is safe during the migration, we recommend to make a backup of your data and all configuration files (such as `pg_hba.conf`, `postgresql.conf`, `postgresql.auto.conf`) using the tool of your choice. The backup process is out of scope of this document. You can use `pg_dumpall` or other tools of your choice. For more information, see the blog post [PostgreSQL Upgrade Using pg_dumpall :octicons-link-external-16:](https://www.percona.com/blog/postgresql-upgrade-using-pg_dumpall/) by _Avinash Vallarapu_, _Fernando Laudares Camargos_, _Jobin Augustine_ and _Nickolay Ihalainen_.
 
     Run **all** commands as root or via **sudo**:
     {.power-number}
@@ -49,7 +48,6 @@ Depending on your business requirements, you may migrate to Percona Distribution
            $ sudo systemctl start postgresql.service
            ```
 
-
 === ":material-redhat: On RHEL and derivatives"
 
        > To ensure that your data is safe during the migration, we recommend to make a backup of your data and all configuration files (such as `pg_hba.conf`, `postgresql.conf`, `postgresql.auto.conf`) using the tool of your choice. The backup process is out of scope of this document. You can use `pg_dumpall` or other tools of your choice. 
@@ -84,15 +82,13 @@ Depending on your business requirements, you may migrate to Percona Distribution
           $ sudo systemctl start postgresql-{{pgversion}}
           ```
 
-
 ## Migrate on a different server
 
 In this scenario, we will refer to the server with PostgreSQL Community as the "source" and to the server with Percona Distribution for PostgreSQL as the "target".
 
 To migrate from PostgreSQL Community to Percona Distribution for PostgreSQL on a different server, do the following:
 
-**On the source server**:
-{.power-number}
+### **On the source server** {.power-number}
 
 1. Back up your data and all configuration files (such as `pg_hba.conf`, `postgresql.conf`, `postgresql.auto.conf`) using the tool of your choice.
 2. Stop the `postgresql` service
@@ -109,12 +105,11 @@ To migrate from PostgreSQL Community to Percona Distribution for PostgreSQL on a
          $ sudo systemctl stop postgresql-{{pgversion}}
          ```
 
-3. Optionally, remove PostgreSQL Community packages 
+3. Optionally, remove PostgreSQL Community packages
 
-**On the target server**:
-{.power-number}
+### **On the target server** {.power-number}
 
-1. [Install percona-release :octicons-link-external-16:](https://docs.percona.com/percona-software-repositories/installing.html) 
+1. [Install percona-release :octicons-link-external-16:](https://docs.percona.com/percona-software-repositories/installing.html)
 2. Enable the repository
 
     ```{.bash data-prompt="$"}
@@ -135,4 +130,4 @@ To migrate from PostgreSQL Community to Percona Distribution for PostgreSQL on a
 
          ```{.bash data-prompt="$"}
          $ sudo systemctl start postgresql-{{pgversion}}
-         ```
+         ```

docs/postgresql-server.md

@@ -1,12 +1,18 @@
 # Percona Server for PostgreSQL
 
-Percona Server for PostgreSQL is a binary-compatible, open source drop-in replacement for PostgreSQL 17. It introduces additional features to the upstream server, including:
+Percona Server for PostgreSQL is a binary-compatible, open source drop-in replacement for PostgreSQL 17. It introduces additional features on top of the upstream server, including:
 
-* Storage Manager (SMGR) API Exposure: Allows PostgreSQL extensions to integrate custom storage managers. This change was inspired by the [patchset](https://www.postgresql.org/message-id/flat/CAJ7c6TOqqrzjYsU6LgDkcJ0yVgzdkx2juJjgAjzP2jPOpZ1qUA%40mail.gmail.com#8e68cfc57fcac14c8e24b00b41e61baf) introduced to the community.
-* WAL Read/Write API Exposure to hook into WAL read and write functions.
+* Storage Manager (SMGR) API Exposure: Allows PostgreSQL extensions to integrate custom storage managers. This change was inspired by the [patchset :octicons-link-external-16:](https://www.postgresql.org/message-id/flat/CAJ7c6TOqqrzjYsU6LgDkcJ0yVgzdkx2juJjgAjzP2jPOpZ1qUA%40mail.gmail.com#8e68cfc57fcac14c8e24b00b41e61baf) introduced to the community.
+* WAL Read/Write API Exposure: Allows extensions to hook into WAL read and write functions.
 
-These modifications have no impact on existing use cases and operation of PostgreSQL. They are required to enable additional encryption capabilities such as index-level and Write-Ahead Logging (WAL) encryption of indexes through the [`pg_tde` :octicons-link-external-16:](https://docs.percona.com/pg-tde/index.html) extension. These encryption features provided by the `pg_tde` are still under active development and are planned for future releases.
+These changes do not affect existing use cases and PostgreSQL behavior. They enable additional encryption features, such as index-level and Write-Ahead Logging (WAL) encryption, through the [`pg_tde` :octicons-link-external-16:](https://docs.percona.com/pg-tde/index.html) extension.
 
-Percona Server and upstream PostgreSQL function identically enabling you to migrate from one to another. 
+Percona Server and the upstream PostgreSQL operate identically, making migrations between the two straightforward.
 
-[Get started :material-arrow-right:](installing.md){.md-button}
+[Get started :material-arrow-right:](installing.md){.md-button}
+
+!!! note
+
+    The PostgreSQL Compatibility Index [(PCI)](https://pgscorecard.com/) test suite reported **100% compatibility**. PCI validates behavioral equivalence by running a suite of compatibility checks against upstream PostgreSQL.
+
+    These results were obtained using [Percona Server for PostgreSQL 17.6.1 :octicons-link-external-16:](https://docs.percona.com/postgresql/17/index.html). [View the PCI test results here :octicons-link-external-16:](https://github.com/secp256k1-sha256/postgres-compatibility-index/blob/main/postgres-compatibility-index/outputs/Percona.json).

docs/solutions/tde-tools-compatibility.md

@@ -153,6 +153,4 @@ operate at the SQL and memory level.
 - TDE does not change their functionality.
 - No additional configuration is required.
 
-## See also
-
-- [Percona `pg_tde` documentation](https://docs.percona.com/postgresql/pg_tde)
+For more information see the [`pg_tde` documentation](https://docs.percona.com/pg-tde/index.html).