Merge pull request #4433 from ClickHouse/db-pipes/rls

DB Pipes: Mention RLS

Author: Amogh-Bharadwaj

docs/integrations/data-ingestion/clickpipes/postgres/faq.md

@@ -339,3 +339,9 @@ Note that TRUNCATE operations are ignored by ClickPipes and will not be replicat
 ### Why can I not replicate my table which has a dot in it? {#replicate-table-dot}
 PeerDB has a limitation currently where dots in source table identifiers - aka either schema name or table name - is not supported for replication as PeerDB cannot discern, in that case, what is the schema and what is the table as it splits on dot.
 Effort is being made to support input of schema and table separately to get around this limitation.
+
+### Initial load completed but there is no/missing data on ClickHouse. What could be the issue? {#initial-load-issue}
+If your initial load has completed without error but your destination ClickHouse table is missing data, it might be that you have RLS (Row Level Security) policies enabled on your source Postgres tables.
+Also worth checking:
+- If the user has sufficient permissions to read the source tables.
+- If there are any row policies on ClickHouse side which might be filtering out rows.

docs/integrations/data-ingestion/clickpipes/postgres/source/supabase.md

@@ -77,6 +77,12 @@ The connection pooler is not supported for CDC based replication, hence it needs
 
 :::
 
+## Note on RLS {#note-on-rls}
+The ClickPipes Postgres user must not be restricted by RLS policies, as it can lead to missing data. You can disable RLS policies for the user by running the below command:
+```sql
+ALTER USER clickpipes_user BYPASSRLS;
+```
+
 ## What's next? {#whats-next}
 
 You can now [create your ClickPipe](../index.md) and start ingesting data from your Postgres instance into ClickHouse Cloud.