Merge pull request #274986 from nachoalonsoportillo/patch-1

Update concepts-query-store.md

Author: v-dirichards

articles/postgresql/flexible-server/concepts-query-store.md

@@ -276,6 +276,8 @@ This function discards all statistics gathered so far by Query Store. It discard
 
 This function discards all statistics gathered in-memory by Query Store (that is, the data in memory that hasn't been flushed yet to the on disk tables supporting persistence of collected data for Query Store). This function can only be executed by the server admin role (**azure_pg_admin**).
 
+## Limitations and known issues
+[!INCLUDE [Note Query store and Azure storage compability](includes/note-query-store-azure-storage-compability.md)]
 
 ### Read-only mode
 When an Azure Database for PostgreSQL - Flexible Server instance is in read-only mode, such as when the `default_transaction_read_only` parameter is set to `on`, or if read-only mode is [automatically enabled due to reaching storage capacity](concepts-limits.md#storage), Query Store does not capture any data.

articles/postgresql/flexible-server/includes/note-query-store-azure-storage-compability.md

@@ -0,0 +1,24 @@
+---
+author: AlicjaKucharczyk
+ms.service: postgresql
+ms.subservice: flexible-server
+ms.topic: include
+ms.date: 01/22/2024
+ms.author: alkuchar
+---
+
+### Azure Storage and Query Store compatibility
+
+Because of compatibility issues, you can't enable Azure Storage and Query Store extensions at the same time. To ensure proper functioning and avoid potential conflicts, enable only one of these extensions at a time.
+
+To use Azure Storage:
+
+* Disable Query Store by setting the parameter `pg_qs.query_capture_mode` to `NONE`. This parameter is dynamic, so you don't need to restart.
+
+To use Query Store:
+
+1. Disable the Azure Storage extension by issuing `DROP EXTENSION azure_storage;`.
+1. Remove Azure Storage from `shared_preload_libraries`.
+1. Restart your database server.
+
+These steps are necessary to prevent conflicts and to ensure that your system operates correctly. We're working to resolve these compatibility issues and will keep you informed of any updates.