Merge pull request #263797 from AlicjaKucharczyk/20240122-querystorestorage

compat

Author: v-regandowner

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

@@ -277,8 +277,10 @@ 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.
+### 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.
 
 ## Related content
 

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 compatibility
+
+Due to compatibility issues, the Query store and Azure storage extensions can't 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 parameter is dynamic, so 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 `shared_preload_libraries`. Restart your database server after this change.
+ 
+These steps are necessary to prevent conflicts and ensure your system operates correctly. We're working to resolve these compatibility issues and will keep you informed of any updates in future releases.