Merge pull request #263254 from nachoalonsoportillo/patch-40

Remove Note until fix to mapping of CmdType enum values is made in view

Author: prmerger-automator[bot]

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

@@ -221,10 +221,6 @@ This view returns all the data that has already been persisted in the supporting
 | query_type | text | | Type of operation represented by the query. Possible values are `unknown`, `select`, `update`, `insert`, `delete`, `merge`, `utility`, `nothing`, `undefined`. |
 
 
-> [!NOTE]  
-> If you have pg_qs enabled and collecting data on an instance of PostgreSQL running a major version <= 14, and perform an [in-place major version upgrade](./concepts-major-version-upgrade.md) to any version >= 15, know that the values returned in the query_type column of query_store.qs_view for any newly created time windows can be considered correct. However, for all the time windows which were created when the version of the engine was <= 14, where it reports `merge` it corresponds to `utility`, and when it reports `nothing` it corresponds to `utility`. The reason for that inconsistency has to do with the way [MERGE statement was implemented in PostgreSQL](https://github.com/postgres/postgres/commit/7103ebb7aae8ab8076b7e85f335ceb8fe799097c), which, instead of appending a new item to the existing ones in the CmdType enum, interleaved an item for MERGE between DELETE and UTILITY.
-
-
 #### query_store.query_texts_view
 
 This view returns query text data in Query Store. There's one row for each distinct query_sql_text.