compat

Author: Alicja Kucharczyk

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

@@ -277,6 +277,7 @@ This function discards all statistics gathered in-memory by Query Store (that is
 
 
 ## Limitations and known issues
+[!INCLUDE [Note Query store and Azure storage compability](includes/note-query-store-azure-storage-compability.md)]
 
 - If an Azure Database for PostgreSQL flexible server instance has the parameter `default_transaction_read_only` set to on, Query Store doesn't capture any data.
 

articles/postgresql/flexible-server/concepts-storage-extension.md

@@ -197,6 +197,9 @@ When the Azure Database for PostgreSQL flexible server administrator decides tha
 SELECT * FROM azure_storage.account_user_remove('mystorageaccount', 'support');
 ```
 
+## Limitations and known issues
+[!INCLUDE [Note Query store and Azure storage compability](includes/note-query-store-azure-storage-compability.md)]
+
 ## Next steps
 
 - If you don't see an extension that you'd like to use, let us know. Vote for existing requests or create new feedback requests in our [feedback forum](https://feedback.azure.com/d365community/forum/c5e32b97-ee24-ec11-b6e6-000d3a4f0da0).

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

@@ -0,0 +1,17 @@
+---
+author: AlicjaKucharczyk
+ms.service: postgresql
+ms.subservice: flexible-server
+ms.topic: include
+ms.date: 01/22/2024
+ms.author: alkuchar
+---
+### Query store and Azure storage compability
+
+Due to compatibility issues, the Query store and Azure storage extensions cannot be enabled at the same time. Users are advised to enable only one of these extensions at a time to ensure proper functioning and avoid potential conflicts.
+ 
+* **To use Azure storage**: Disable the query store by setting the parameter `pg_qs.query_capture_mode` to `NONE`. This is a dynamic parameter, no restart is needed.
+ 
+* **To use Query store**: Disable the azure storage extension by issuing `DROP EXTENSION azure_storage;`. Additionally, remove Azure storage from the the `shared_preload_libraries`. Restart your database server after this change.
+ 
+Please be aware that these steps are necessary to prevent conflicts and ensure your system operates correctly. We are working to resolve these compatibility issues and will keep you informed of any updates in future releases.