Note the limitations of concurrent function

Author: jonels-msft

articles/cosmos-db/postgresql/quickstart-distribute-tables.md

@@ -8,7 +8,7 @@ ms.service: cosmos-db
 ms.subservice: postgresql
 ms.custom: mvc, mode-ui, ignite-2022
 ms.topic: quickstart
-ms.date: 10/28/2022
+ms.date: 11/01/2022
 ---
 
 # Create and distribute tables
@@ -73,13 +73,10 @@ increased storage and compute performance.
 
 > [!NOTE]
 >
-> If your workload fits in 64 vCores, 256GB RAM and 2TB storage, you can use a
-> single-node cluster. In this case, distributing tables is optional. Later,
-> you can distribute tables as needed using
+> In real applications, when your workload fits in 64 vCores, 256GB RAM and 2TB
+> storage, you can use a single-node cluster. In this case, distributing tables
+> is optional. Later, you can distribute tables as needed using
 > [create_distributed_table_concurrently](reference-functions.md#create_distributed_table_concurrently).
->
-> This quickstart demonstrates distributing tables, despite the small example
-> dataset.
 
 Let's distribute the tables:
 

articles/cosmos-db/postgresql/reference-functions.md

@@ -6,7 +6,7 @@ author: jonels-msft
 ms.service: cosmos-db
 ms.subservice: postgresql
 ms.topic: reference
-ms.date: 10/28/2022
+ms.date: 11/01/2022
 ---
 
 # Azure Cosmos DB for PostgreSQL functions
@@ -99,6 +99,19 @@ This function has the same interface and purpose as
 [create_distributed_function](#create_distributed_table), but doesn't block
 writes during table distribution.
 
+However, `create_distributed_table_concurrently` has a few limitations:
+
+* You can't use the function in a transaction block, which means you can only
+  distribute one table at a time. (You *can* use the function on
+  time-partitioned tables, though.)
+* You can't use `create_distributed_table_concurrently` when the table is
+  referenced by a foreign key, or references another local table. However,
+  foreign keys to reference tables work, and you can create foreign keys to other
+  distributed tables after table distribution completes.
+* If you don't have a primary key or replica identity on your table, then
+  update and delete commands will fail during the table distribution due to
+  limitations on logical replication.
+
 ### truncate\_local\_data\_after\_distributing\_table
 
 Truncate all local rows after distributing a table, and prevent constraints