Merge pull request #259326 from AlicjaKucharczyk/20231122-readreplicarestapi

tabular

Author: Stacyrch140

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

@@ -1484,6 +1484,11 @@
         "source_path_from_root": "/articles/postgresql/flexible-server/concepts-networking.md",
         "redirect_url": "/azure/postgresql/flexible-server/concepts-networking-private",
         "redirect_document_id": true
+    },
+    {
+        "source_path_from_root": "/articles/postgresql/flexible-server/how-to-read-replicas-rest-api.md",
+        "redirect_url": "/azure/postgresql/flexible-server/how-to-read-replicas-portal",
+        "redirect_document_id": true
     }
     ]
 }

articles/postgresql/TOC.yml

@@ -391,12 +391,9 @@
             href: flexible-server/how-to-enable-intelligent-performance-cli.md
     - name: Replication
       items:
-      - name: Azure portal
+      - name: Azure portal, REST API
         href: flexible-server/how-to-read-replicas-portal.md
         displayName: replica
-      - name: Azure REST API
-        href: flexible-server/how-to-read-replicas-rest-api.md
-        displayName: replica rest api
   - name: Extensions
     items:
     - name: Overview

articles/postgresql/flexible-server/concepts-read-replicas.md

@@ -38,7 +38,7 @@ Because replicas are read-only, they don't directly reduce write-capacity burden
 
 ### Considerations
 
-The feature is meant for scenarios where the lag is acceptable and meant for offloading queries. It isn't meant for synchronous replication scenarios where the replica data is expected to be up-to-date. There will be a measurable delay between the primary and the replica. This delay can be in minutes or even hours, depending on the workload and the latency between the primary and the replica. Typically, read replicas in the same region as the primary has less lag than geo-replicas, as the latter often deals with geographical distance-induced latency. For more insights into the performance implications of geo-replication, refer to [Geo-replication](#geo-replication) section. The data on the replica eventually becomes consistent with the data on the primary. Use this feature for workloads that can accommodate this delay.
+Read replicas are primarily designed for scenarios where offloading queries is beneficial, and a slight lag is manageable. They are optimized to provide near realtime updates from the primary for most workloads, making them an excellent solution for read-heavy scenarios. However, it's important to note that they are not intended for synchronous replication scenarios requiring up-to-the-minute data accuracy. While the data on the replica eventually becomes consistent with the primary, there may be a delay, which typically ranges from a few seconds to minutes, and in some heavy workload or high-latency scenarios, this could extend to hours. Typically, read replicas in the same region as the primary has less lag than geo-replicas, as the latter often deals with geographical distance-induced latency. For more insights into the performance implications of geo-replication, refer to [Geo-replication](#geo-replication) section. The data on the replica eventually becomes consistent with the data on the primary. Use this feature for workloads that can accommodate this delay.
 
 > [!NOTE]  
 > For most workloads, read replicas offer near-real-time updates from the primary. However, with persistent heavy write-intensive primary workloads, the replication lag could continue to grow and might only be able to catch up with the primary. This might also increase storage usage at the primary as the WAL files are only deleted once received at the replica. If this situation persists, deleting and recreating the read replica after the write-intensive workloads are completed, you can bring the replica back to a good state for lag.

articles/postgresql/flexible-server/how-to-read-replicas-portal.md

@@ -4,8 +4,8 @@ description: This article describes how to stop/start operations in Azure Databa
 ms.service: postgresql
 ms.subservice: flexible-server
 ms.custom: devx-track-azurecli
-ms.author: sunila
-author: sunilagarwal
+author: AlicjaKucharczyk
+ms.author: alkuchar
 ms.reviewer: ""
 ms.topic: how-to
 ms.date: 11/30/2021
@@ -21,7 +21,7 @@ This article shows you how to perform restart, start and stop flexible server us
 
 - If you don't have an Azure subscription, create a [free](https://azure.microsoft.com/free/) account before you begin.
 - Install or upgrade Azure CLI to the latest version. See [Install Azure CLI](/cli/azure/install-azure-cli).
--  Login to Azure account using [az login](/cli/azure/reference-index#az-login) command. Note the **id** property, which refers to **Subscription ID** for your Azure account.
+-  Log in to Azure account using [az login](/cli/azure/reference-index#az-login) command. Note the **id** property, which refers to **Subscription ID** for your Azure account.
 
     ```azurecli-interactive
     az login
@@ -33,14 +33,14 @@ This article shows you how to perform restart, start and stop flexible server us
     az account set --subscription <subscription id>
     ```
 
-- Create a PostgreSQL Flexible Server if you have not already created one using the ```az postgres flexible-server create``` command.
+- Create a PostgreSQL Flexible Server if you haven't already created one using the ```az postgres flexible-server create``` command.
 
     ```azurecli
     az postgres flexible-server create --resource-group myresourcegroup --name myservername
     ```
 
 ## Stop a running server
-To stop a server, run  ```az postgres flexible-server stop``` command. If you are using [local context](/cli/azure/config/param-persist), you don't need to provide any arguments.
+To stop a server, run  ```az postgres flexible-server stop``` command. If you're using [local context](/cli/azure/config/param-persist), you don't need to provide any arguments.
 
 **Usage:**
 ```azurecli
@@ -60,7 +60,7 @@ az postgres flexible-server stop
 ```
 
 ## Start a stopped server
-To start a server, run  ```az postgres flexible-server start``` command. If you are using [local context](/cli/azure/config/param-persist), you don't need to provide any arguments.
+To start a server, run  ```az postgres flexible-server start``` command. If you're using [local context](/cli/azure/config/param-persist), you don't need to provide any arguments.
 
 **Usage:**
 ```azurecli

articles/postgresql/flexible-server/how-to-read-replicas-rest-api.md

@@ -1,7 +1,7 @@
 ---
 title: 'Quickstart: Create an Azure Database for PostgreSQL Flexible Server - Azure libraries (SDK) for Python'
 description: In this Quickstart, learn how to create an Azure Database for PostgreSQL Flexible server using Azure libraries (SDK) for Python.
-author: AwdotiaRomanowna
+author: AlicjaKucharczyk
 ms.service: postgresql
 ms.subservice: flexible-server
 ms.custom: devx-track-python-sdk
@@ -61,11 +61,12 @@ def create_postgres_flexible_server(subscription_id, resource_group, server_name
 
     # Create PostgreSQL Flexible Server
     server_params = Server(
+        location='<location>',
         sku=Sku(name='Standard_D4s_v3', tier='GeneralPurpose'),
         administrator_login='pgadmin',
         administrator_login_password='<mySecurePassword>',
         storage=Storage(storage_size_gb=32),
-        version="14",
+        version="16",
         create_mode="Create"
     )
 
@@ -82,7 +83,6 @@ if __name__ == '__main__':
     subscription_id = '<subscription_id>'
     resource_group = '<resource_group>'
     server_name = '<servername>'
-    location = 'eastus'
 
     create_postgres_flexible_server(subscription_id, resource_group, server_name, location)
 
@@ -92,11 +92,12 @@ Replace the following parameters with your data:
 
 - **subscription_id**: Your own [subscription ID](../../azure-portal/get-subscription-tenant-id.md#find-your-azure-subscription).
 - **resource_group**: The name of the resource group you want to use. The script will create a new resource group if it doesn't exist.   
-- **server_name**: A unique name that identifies your Azure Database for PostgreSQL server. The domain name `postgres.database.azure.com` is appended to the server name you provide. The server name must be at least 3 characters and at most 63 characters, and can only contain lowercase letters, numbers, and hyphens.
+- **server_name**: A unique name that identifies your Azure Database for PostgreSQL - Flexible Server. The domain name `postgres.database.azure.com` is appended to the server name you provide. The server name must be at least 3 characters and at most 63 characters, and can only contain lowercase letters, numbers, and hyphens.
+- **location**: The Azure region where you want to create your Azure Database for PostgreSQL - Flexible Server. It defines the geographical location where your server and its data reside. Choose a region close to your users for reduced latency. The location should be specified in the format of Azure region short names, like `westus2`, `eastus`, or `northeurope`.
 - **administrator_login**: The primary administrator username for the server. You can create additional users after the server has been created.
 - **administrator_login_password**: A password for the primary administrator for the server. It must contain between 8 and 128 characters. Your password must contain characters from three of the following categories: English uppercase letters, English lowercase letters, numbers (0 through 9), and non-alphanumeric characters (!, $, #, %, etc.).
 
-You can also customize other parameters like location, storage size, engine version, etc.
+You can also customize other parameters like storage size, engine version, etc.
 
 
 > [!NOTE]