Isolate columnar limitations on concept page

Author: jonels-msft

articles/cosmos-db/postgresql/concepts-columnar.md

@@ -194,7 +194,27 @@ storage](https://docs.citusdata.com/en/stable/use_cases/timeseries.html#archivin
 
 ## Limitations
 
-[!INCLUDE[columnar-limitations](includes/columnar-limitations.md)]
+This feature still has significant limitations:
+
+* Compression is on disk, not in memory
+* Append-only (no UPDATE/DELETE support)
+* No space reclamation (for example, rolled-back transactions may still consume
+  disk space)
+* No index support, index scans, or bitmap index scans
+* No tidscans
+* No sample scans
+* No TOAST support (large values supported inline)
+* No support for ON CONFLICT statements (except DO NOTHING actions with no
+  target specified).
+* No support for tuple locks (SELECT ... FOR SHARE, SELECT ... FOR UPDATE)
+* No support for serializable isolation level
+* Support for PostgreSQL server versions 12+ only
+* No support for foreign keys, unique constraints, or exclusion constraints
+* No support for logical decoding
+* No support for intra-node parallel scans
+* No support for AFTER ... FOR EACH ROW triggers
+* No UNLOGGED columnar tables
+* No TEMPORARY columnar tables
 
 ## Next steps
 

articles/cosmos-db/postgresql/includes/columnar-limitations.md

@@ -83,13 +83,6 @@ cluster, the `citus` database. Creating another
 database is currently not allowed, and the CREATE DATABASE command will fail
 with an error.
 
-### Columnar storage
-
-Azure Cosmos DB for PostgreSQL currently has these limitations with [columnar
-tables](concepts-columnar.md):
-
-[!INCLUDE[columnar-limitations](includes/columnar-limitations.md)]
-
 ## Next steps
 
 * Learn how to [create a cluster in the