Merge pull request #280137 from niklarin/cpg-july02

Azure Cosmos DB for PostgreSQL - multiple small updates

Author: prmerger-automator[bot]

articles/cosmos-db/postgresql/concepts-security-overview.md

@@ -1,12 +1,12 @@
 ---
 title: Security overview - Azure Cosmos DB for PostgreSQL
 description: Information protection and network security for Azure Cosmos DB for PostgreSQL.
-ms.author: jonels
-author: jonels-msft
+ms.author: nlarin
+author: niklarin
 ms.service: cosmos-db
 ms.subservice: postgresql
 ms.topic: conceptual
-ms.date: 01/14/2022
+ms.date: 07/04/2024
 ---
 
 # Security in Azure Cosmos DB for PostgreSQL
@@ -19,7 +19,9 @@ This page outlines the multiple layers of security available to protect the data
 
 ### In transit
 
-Whenever data is ingested into a node, Azure Cosmos DB for PostgreSQL secures your data by encrypting it in-transit with Transport Layer Security 1.2. Encryption (SSL/TLS) is always enforced, and can’t be disabled.
+Whenever data is ingested into a node, Azure Cosmos DB for PostgreSQL secures your data by encrypting it in-transit with Transport Layer Security (TLS) 1.2 or higher. Encryption (SSL/TLS) is always enforced, and can’t be disabled.
+
+The minimum TLS version required to connect to the cluster might be enforced by setting **ssl_min_protocol_version** coordinator and worker node parameter to *TLSV1.2* or *TLSV1.3* for TLS 1.2 or TLS 1.3 respectively.  
 
 ### At rest
 

articles/cosmos-db/postgresql/howto-scale-initial.md

@@ -1,20 +1,20 @@
 ---
 title: Initial cluster size - Azure Cosmos DB for PostgreSQL
 description: Pick the right initial size for your use case
-ms.author: jonels
-author: jonels-msft
+ms.author: nlarin
+author: niklarin
 ms.service: cosmos-db
 ms.subservice: postgresql
 ms.topic: how-to
-ms.date: 01/30/2023
+ms.date: 07/04/2024
 ---
 
 # Pick initial size for cluster in Azure Cosmos DB for PostgreSQL
 
 [!INCLUDE [PostgreSQL](../includes/appliesto-postgresql.md)]
 
 The size of a cluster, both number of nodes and their hardware capacity,
-is [easy to change](howto-scale-grow.md)). However you still need to
+is [easy to change](howto-scale-grow.md). However you still need to
 choose an initial size for a new cluster. Here are some tips for a
 reasonable choice.
 

articles/cosmos-db/postgresql/howto-upgrade.md

@@ -1,12 +1,12 @@
 ---
 title: Upgrade cluster - Azure Cosmos DB for PostgreSQL
 description: See how you can upgrade PostgreSQL and Citus in Azure Cosmos DB for PostgreSQL.
-ms.author: jonels
-author: jonels-msft
+ms.author: nlarin
+author: niklarin
 ms.service: cosmos-db
 ms.subservice: postgresql
 ms.topic: how-to
-ms.date: 01/30/2023
+ms.date: 07/04/2024
 ---
 
 # Upgrade cluster in Azure Cosmos DB for PostgreSQL
@@ -45,6 +45,19 @@ works properly, upgrade the original cluster.
 > [!NOTE]
 > If you're already running the latest PostgreSQL version, the selection and button are grayed out.
 
+## Post-upgrade tasks
+
+After a major PostgreSQL version upgrade, run the `ANALYZE` operation to refresh the `pg_statistic` table. `pg_statistic` is a system catalog table in PostgreSQL that stores statistical data about the content of table columns and index expressions. Entries in `pg_statistic` are created by the [ANALYZE](https://www.postgresql.org/docs/16/sql-analyze.html) command and used by the query planner.
+
+Run the `ANALYZE` command without any parameters to generate statistics for the tables in the database on your cluster. The default database name is 'citus'. If custom database name was used at the cluster creation time, you can find it on the **Overview** page of your cluster's properties. Using the optional `VERBOSE` flag allows you to see the progress.
+
+```sql
+ANALYZE VERBOSE;
+```
+
+> [!NOTE]
+> Database performance might be impacted if you don't run `ANALYZE` operation after the major PostgreSQL version upgrade on your cluster.
+
 ## Next steps
 
 * Learn about [supported PostgreSQL versions](reference-versions.md).