Merge pull request #1295 from MicrosoftDocs/main

Publish to live, Sunday 4 AM PST, 1/26

Author: ttorble

articles/cosmos-db/how-to-always-encrypted.md

@@ -36,6 +36,9 @@ You can:
 - Create one DEK per property to encrypt, or
 - Use the same DEK to encrypt multiple properties.
 
+> [!NOTE]
+> Resource limit for Client Encryption Key is 20
+
 #### Customer-managed keys
 
 Before DEKs get stored in Azure Cosmos DB, they are wrapped by a customer-managed key (CMK). By controlling the wrapping and unwrapping of DEKs, CMKs effectively control the access to the data that's encrypted with their corresponding DEKs. CMK storage is designed as an extensible, with a default implementation that expects them to be stored in Azure Key Vault.

articles/postgresql/.openpublishing.redirection.postgresql.json

@@ -1984,6 +1984,21 @@
         "source_path_from_root": "/articles/postgresql/flexible-server/how-to-scale-compute-storage-portal.md",
         "redirect_url": "/azure/postgresql/flexible-server/how-to-scale-compute",
         "redirect_document_id": false
+    },
+    {
+        "source_path_from_root": "/articles/postgresql/flexible-server/how-to-restore-to-different-subscription-or-resource-group.md",
+        "redirect_url": "/azure/postgresql/flexible-server/how-to-restore-server",
+        "redirect_document_id": false
+    },
+    {
+        "source_path_from_root": "/articles/postgresql/flexible-server/how-to-restore-different-subscription-resource-group-api.md",
+        "redirect_url": "/azure/postgresql/flexible-server/how-to-restore-server",
+        "redirect_document_id": false
+    },
+    {
+        "source_path_from_root": "/articles/postgresql/flexible-server/how-to-restore-server-cli.md",
+        "redirect_url": "/azure/postgresql/flexible-server/how-to-restore-server",
+        "redirect_document_id": false
     }
 ]
 }

articles/postgresql/TOC.yml

@@ -433,12 +433,6 @@
         items:
         - name: Restore a dropped server
           href: flexible-server/how-to-restore-dropped-server.md
-      - name: Cross subscription and cross resource group restore
-        items:
-        - name: Azure portal
-          href: flexible-server/how-to-restore-to-different-subscription-or-resource-group.md
-        - name: Azure REST API
-          href: flexible-server/how-to-restore-different-subscription-resource-group-api.md 
       - name: Relocate a server 
         href: /azure/operational-excellence/relocation-postgresql-flexible-server?toc=/azure/postgresql/toc.json
     - name: Networking

articles/postgresql/extensions/concepts-extensions-by-engine.md

@@ -4,7 +4,7 @@ description: Introduction to the PostgreSQL extensions in Azure Database for Pos
 author: varun-dhawan
 ms.author: varundhawan
 ms.reviewer: maghan
-ms.date: 01/12/2025
+ms.date: 01/25/2025
 ms.service: azure-database-postgresql
 ms.subservice: flexible-server
 ms.topic: how-to
@@ -112,31 +112,69 @@ az postgres flexible-server restart --resource-group <resource_group> --name <se
 
 ## Create extensions
 
-After an extension is allowlisted and, if the extension requires it, is also added to `shared_load_libraries`, it can be created or installed in each database on which it's to be used.
+1. [Allowlist](#allow-extensions) the extension.
 
-1. To create an extension, a user must be a member of the `azure_pg_admin` role.
+1. If the extension requires it, also add it to `shared_load_libraries`.
+
+1. The user that creates the extensions must be a member of the `azure_pg_admin` role.
 
 1. Run the [CREATE EXTENSION](https://www.postgresql.org/docs/current/sql-createextension.html) command to create or install a particular extension. This command loads the packaged objects into your database.
 
+```sql
+CREATE EXTENSION <extension>;
+```
+
+1. Some extensions require other extensions to be created first, because they depend on objects distributed by those other extensions. It's the case, for example, of the `pg_diskann` extension, which has dependencies on the `vector` extension. To install such extensions, you can proceed in two ways:
+    - [Allowlist](#allow-extensions) and run `CREATE EXTENSION` on the depending extension first. Then, allowlist and run `CREATE EXTENSION` on the dependent extension.
+
+    ```sql
+    CREATE EXTENSION <depending_extension>;
+    CREATE EXTENSION <dependent_extension>;
+    ```
+    
+    - [Allowlist](#allow-extensions) and run `CREATE EXTENSION` on the dependent extension only, but add the `CASCADE` clause, so that it automatically creates all extensions on which it depends.
+
+    ```sql
+    CREATE EXTENSION <dependent_extension> CASCADE;
+    ```
+    
 > [!NOTE]  
 > Third-party extensions offered in Azure Database for PostgreSQL flexible server are open-source licensed code. We don't offer any third-party extensions or extension versions with premium or proprietary licensing models.
 
 Azure Database for PostgreSQL flexible server instance supports a subset of key PostgreSQL extensions, as listed in [supported extensions by name](concepts-extensions-versions.md) or in [supported extensions by version of PostgreSQL](concepts-extensions-by-engine.md). This information is also available by running `SHOW azure.extensions;`. Extensions not included in those lists aren't supported on Azure Database for PostgreSQL flexible server. You can't create or load your own extensions in Azure Database for PostgreSQL flexible server.
 
 ## Drop extensions
 
-To drop an extension, first make sure to [allowlist](#allow-extensions) it.
+1. [Allowlist](#allow-extensions) the extension.
 
-1. To drop an extension, a user must be a member of the `azure_pg_admin` role.
+1. The user that drops the extensions must be a member of the `azure_pg_admin` role.
 
 1. Run the [DROP EXTENSION](https://www.postgresql.org/docs/current/sql-dropextension.html) command to drop or uninstall a particular extension. This command drops the objects packaged in the extension from your database.
 
+```sql
+DROP EXTENSION <extension>;
+```
+
+1. Some extensions might distribute objects which are required by other extension. That's the case, for example, of the `vector` extension, in which the `pg_diskann` extension depends. To drop such extensions, you can proceed in two ways:
+    - [Allowlist](#allow-extensions) and run `DROP EXTENSION` on all the extensions that depend on the one that you're trying to drop first. Then, allowlist and run `DROP EXTENSION` on the extension on which other extensions depended.
+
+    ```sql
+    DROP EXTENSION <dependent_extension>;
+    DROP EXTENSION <depending_extension>;
+    ```
+
+    - [Allowlist](#allow-extensions) and run `DROP EXTENSION` on the extension that you want to drop, that other extensions depend on, but add the `CASCADE` clause, so that it automatically drops all extensions on which it depends.
+
+    ```sql
+    DROP EXTENSION <depending_extension> CASCADE;
+    ```
+
 ## Update extensions
 
 To update an installed extension to the latest available version supported by Azure, use the following SQL command:
 
 ```sql
-ALTER EXTENSION <extension_name> UPDATE;
+ALTER EXTENSION <extension> UPDATE;
 ```
 
 This command simplifies the management of database extensions by allowing users to manually upgrade to the latest version approved by Azure, enhancing both compatibility and security.

articles/postgresql/extensions/how-to-allow-extensions.md

@@ -2,7 +2,7 @@
 author: akashraokm
 ms.author: akashrao
 ms.reviewer: maghan, randolphwest
-ms.date: 12/05/2024
+ms.date: 01/26/2025
 ms.service: azure-database-postgresql
 ms.subservice: flexible-server
 ms.topic: include
@@ -282,6 +282,22 @@ ms.custom: automatically generated
 
 
 
+## hll
+
+[hll](https://github.com/citusdata/postgresql-hll) (Preview) introduces a new data type hll which is a HyperLogLog data structure.
+
+| PostgreSQL version | Extension version |
+| --- | --- |
+| 17 | N/A |
+| 16 | 2.18 |
+| 15 | 2.18 |
+| 14 | 2.18 |
+| 13 | 2.18 |
+| 12 | 2.18 |
+| 11 | N/A |
+
+
+
 ## hstore
 
 [hstore](https://www.postgresql.org/docs/current/hstore.html) is a data type for storing sets of (key, value) pairs.
@@ -304,7 +320,7 @@ ms.custom: automatically generated
 
 | PostgreSQL version | Extension version |
 | --- | --- |
-| 17 | 1.4.0 |
+| 17 | 1.4.1 |
 | 16 | 1.4.0 |
 | 15 | 1.4.0 |
 | 14 | 1.4.0 |
@@ -527,6 +543,22 @@ ms.custom: automatically generated
 
 
 
+## pg_diskann
+
+[pg_diskann](../../flexible-server/how-to-use-pgdiskann.md) (Preview) is a scalable approximate nearest neighbor search algorithm for efficient vector search at any scale.
+
+| PostgreSQL version | Extension version |
+| --- | --- |
+| 17 | N/A |
+| 16 | 0.4.0 |
+| 15 | 0.4.0 |
+| 14 | 0.4.0 |
+| 13 | N/A |
+| 12 | N/A |
+| 11 | N/A |
+
+
+
 ## pg_failover_slots
 
 [pg_failover_slots](https://github.com/EnterpriseDB/pg_failover_slots) is a logical replication slot manager for failover purposes.
@@ -638,11 +670,11 @@ ms.custom: automatically generated
 
 | PostgreSQL version | Extension version |
 | --- | --- |
-| 17 | 1.4.7 |
-| 16 | 1.4.7 |
-| 15 | 1.4.7 |
-| 14 | 1.4.7 |
-| 13 | 1.4.7 |
+| 17 | 1.5.1 |
+| 16 | 1.5.1 |
+| 15 | 1.5.1 |
+| 14 | 1.5.1 |
+| 13 | 1.5.1 |
 | 12 | 1.4.7 |
 | 11 | 1.4.7 |
 
@@ -977,6 +1009,22 @@ ms.custom: automatically generated
 
 
 
+## tdigest
+
+[tdigest](https://github.com/tvondra/tdigest) (Preview) implements t-digest, a data structure for on-line accumulation of rank-based statistics such as quantiles and trimmed means.
+
+| PostgreSQL version | Extension version |
+| --- | --- |
+| 17 | 1.4.2 |
+| 16 | 1.4.2 |
+| 15 | 1.4.2 |
+| 14 | 1.4.2 |
+| 13 | 1.4.2 |
+| 12 | 1.4.2 |
+| 11 | N/A |
+
+
+
 ## tds_fdw
 
 [tds_fdw](https://github.com/tds-fdw/tds_fdw) is a foreign data wrapper for querying a TDS database (SAP ASE or SQL Server).
@@ -999,7 +1047,7 @@ ms.custom: automatically generated
 
 | PostgreSQL version | Extension version |
 | --- | --- |
-| 17 | N/A |
+| 17 | 2.17.2 <sup>*</sup> |
 | 16 | 2.13.0 <sup>*</sup> |
 | 15 | 2.10.0 <sup>*</sup> |
 | 14 | 2.10.0 <sup>*</sup> |
@@ -1009,6 +1057,22 @@ ms.custom: automatically generated
 
 <sup>*</sup> Enable corresponding libraries in the `shared_preload_libraries` server parameter.
 
+## topn
+
+[topn](https://github.com/citusdata/postgresql-topn) (Preview) returns the top values in a database according to some criteria.
+
+| PostgreSQL version | Extension version |
+| --- | --- |
+| 17 | 2.7.0 |
+| 16 | 2.7.0 |
+| 15 | 2.7.0 |
+| 14 | 2.7.0 |
+| 13 | 2.7.0 |
+| 12 | N/A |
+| 11 | N/A |
+
+
+
 ## tsm_system_rows
 
 [tsm_system_rows](https://www.postgresql.org/docs/13/tsm-system-rows.html) is a `TABLESAMPLE` method which accepts number of rows as a limit.

articles/postgresql/extensions/includes/extensions-table.md

@@ -98,6 +98,8 @@ The following options are available for configuring Query Store parameters:
 
 (*) Static server parameter which requires a server restart for a change in its value to take effect. 
 
+> [!NOTE]  
+> If you change the value for `pg_qs.max_query_text_length` parameter, the text of all queries that were captured before you make the change continue to use the same query_id and sql_query_text. It might give the impression that the new value doesn't take effect but, for queries that weren't recorded in query store before, you will see that the query text uses the newly configured maximum length. This is by design, and is explained at [Views and functions](#views-and-functions). If you execute [query_store.qs_reset](#query_storeqs_reset), it removes all the information recorded by query store until now, including the text that was captured for each query id, and if any of those queries is executed again, the newly configured maximum length is applied to the text being captured.
 
 The following options apply specifically to wait statistics: