<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Request for Guidance: Enabling PostgreSQL CDC in Azure Databricks Lakeflow Connect in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/request-for-guidance-enabling-postgresql-cdc-in-azure-databricks/m-p/176337#M57125</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/189296"&gt;@Pravieen&lt;/a&gt;&amp;nbsp;worth looking this page :&amp;nbsp;&lt;A href="https://www.databricks.com/blog/push-based-cdc-unity-catalog-zerobus-ingest-and-debezium" target="_blank"&gt;https://www.databricks.com/blog/push-based-cdc-unity-catalog-zerobus-ingest-and-debezium&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Br&lt;/P&gt;</description>
    <pubDate>Fri, 13 Nov 2026 09:36:50 GMT</pubDate>
    <dc:creator>saurabh18cs</dc:creator>
    <dc:date>2026-11-13T09:36:50Z</dc:date>
    <item>
      <title>Request for Guidance: Enabling PostgreSQL CDC in Azure Databricks Lakeflow Connect</title>
      <link>https://community.databricks.com/t5/data-engineering/request-for-guidance-enabling-postgresql-cdc-in-azure-databricks/m-p/176328#M57122</link>
      <description>&lt;P&gt;Hello Databricks Community,&lt;/P&gt;&lt;P&gt;I am using Azure Databricks Lakeflow Connect with a PostgreSQL source.&lt;/P&gt;&lt;P&gt;The CDC option is disabled in the PostgreSQL ingestion wizard, and I see the following message:&lt;/P&gt;&lt;P&gt;This mode is not available in this workspace for the selected connector.&lt;/P&gt;&lt;P&gt;Could someone clarify how to enable PostgreSQL CDC Public Preview in an Azure Databricks workspace?&lt;/P&gt;&lt;P&gt;I have already raised a support ticket (#01072097).&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Fri, 13 Nov 2026 06:41:30 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/request-for-guidance-enabling-postgresql-cdc-in-azure-databricks/m-p/176328#M57122</guid>
      <dc:creator>Pravieen</dc:creator>
      <dc:date>2026-11-13T06:41:30Z</dc:date>
    </item>
    <item>
      <title>Re: Request for Guidance: Enabling PostgreSQL CDC in Azure Databricks Lakeflow Connect</title>
      <link>https://community.databricks.com/t5/data-engineering/request-for-guidance-enabling-postgresql-cdc-in-azure-databricks/m-p/176329#M57123</link>
      <description>&lt;P class=""&gt;&lt;STRONG&gt;Short answer:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;you can't switch this on from the wizard or a workspace setting. The Azure docs say the PostgreSQL connector is in Public Preview and that you request access through your Azure Databricks account team [1]. "This mode is not available in this workspace for the selected connector" means the preview isn't enabled for your workspace yet. Your support ticket is fine, but also ping your account team (or ask support to route it to them), and include the workspace ID and region.&lt;/P&gt;&lt;P class=""&gt;While you wait, get the PostgreSQL side ready. Then the pipeline works on the first try once access lands.&lt;/P&gt;&lt;H2&gt;1. Turn on logical replication&lt;/H2&gt;&lt;P class=""&gt;The connector reads changes through logical replication, PostgreSQL 13 or later [2].&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;PRE&gt;SHOW wal_level;   -- must return: logical&lt;/PRE&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P class=""&gt;On Azure Database for PostgreSQL Flexible Server, set&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;wal_level = logical&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;in&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Server parameters&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;(portal or CLI) and restart the server. Also open the firewall to your Databricks workspace [2].&lt;/P&gt;&lt;H2&gt;2. Create the replication user, publication and slot&lt;/H2&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;PRE&gt;CREATE USER databricks_replication WITH PASSWORD '&amp;lt;secret&amp;gt;';
GRANT CONNECT ON DATABASE your_db TO databricks_replication;
GRANT USAGE ON SCHEMA your_schema TO databricks_replication;
GRANT SELECT ON TABLE your_schema.your_table TO databricks_replication;
ALTER USER databricks_replication WITH REPLICATION;

-- as the table owner, not the replication user
CREATE PUBLICATION databricks_publication FOR TABLE your_schema.your_table;

-- the slot must be created BY the replication user, pgoutput only
SET ROLE databricks_replication;
SELECT pg_create_logical_replication_slot('databricks_slot', 'pgoutput');
RESET ROLE;&lt;/PRE&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P class=""&gt;Order matters: create the publication first, then the slot [2]. You need one publication and one slot per database.&lt;/P&gt;&lt;H2&gt;3. Don't skip the WAL limits&lt;/H2&gt;&lt;P class=""&gt;Set&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;max_slot_wal_keep_size&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;to a finite value; the default&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;-1&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;lets an idle slot grow WAL without limit. Make sure&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;max_replication_slots&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;and&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;max_wal_senders&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;cover the new slot [2]. If you delete the pipeline later, drop the slot by hand.&lt;/P&gt;&lt;H2&gt;4. Check before you retry the wizard&lt;/H2&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;PRE&gt;SHOW wal_level;
SELECT rolname, rolreplication FROM pg_roles WHERE rolname = 'databricks_replication';
SELECT * FROM pg_publication WHERE pubname = 'databricks_publication';&lt;/PRE&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;H2&gt;What I'd do&lt;/H2&gt;&lt;P class=""&gt;Ask the account team for PostgreSQL connector preview access on that workspace. In parallel, finish steps 1–4. Once it is enabled, create the connection with the replication user's credentials and retry the wizard [3].&lt;/P&gt;&lt;P class=""&gt;Note: I couldn't test this end-to-end because I don't have a PostgreSQL source wired to a workspace with the preview. Everything above comes from the current Azure docs.&lt;/P&gt;&lt;H2&gt;References&lt;/H2&gt;&lt;P class=""&gt;[1] PostgreSQL ingestion connector | Azure Databricks —&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A class="" href="https://learn.microsoft.com/en-us/azure/databricks/ingestion/lakeflow-connect/postgresql" target="_blank" rel="noopener noreferrer"&gt;https://learn.microsoft.com/en-us/azure/databricks/ingestion/lakeflow-connect/postgresql&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;[2] Configure PostgreSQL for ingestion into Azure Databricks —&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A class="" href="https://learn.microsoft.com/en-us/azure/databricks/ingestion/lakeflow-connect/postgresql-source-setup" target="_blank" rel="noopener noreferrer"&gt;https://learn.microsoft.com/en-us/azure/databricks/ingestion/lakeflow-connect/postgresql-source-setup&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=""&gt;[3] Create a PostgreSQL connection | Azure Databricks —&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A class="" href="https://learn.microsoft.com/en-us/azure/databricks/ingestion/lakeflow-connect/postgresql-connection" target="_blank" rel="noopener noreferrer"&gt;https://learn.microsoft.com/en-us/azure/databricks/ingestion/lakeflow-connect/postgresql-connection&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 13 Nov 2026 07:15:09 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/request-for-guidance-enabling-postgresql-cdc-in-azure-databricks/m-p/176329#M57123</guid>
      <dc:creator>VladTamas</dc:creator>
      <dc:date>2026-11-13T07:15:09Z</dc:date>
    </item>
    <item>
      <title>Re: Request for Guidance: Enabling PostgreSQL CDC in Azure Databricks Lakeflow Connect</title>
      <link>https://community.databricks.com/t5/data-engineering/request-for-guidance-enabling-postgresql-cdc-in-azure-databricks/m-p/176337#M57125</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/189296"&gt;@Pravieen&lt;/a&gt;&amp;nbsp;worth looking this page :&amp;nbsp;&lt;A href="https://www.databricks.com/blog/push-based-cdc-unity-catalog-zerobus-ingest-and-debezium" target="_blank"&gt;https://www.databricks.com/blog/push-based-cdc-unity-catalog-zerobus-ingest-and-debezium&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Br&lt;/P&gt;</description>
      <pubDate>Fri, 13 Nov 2026 09:36:50 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/request-for-guidance-enabling-postgresql-cdc-in-azure-databricks/m-p/176337#M57125</guid>
      <dc:creator>saurabh18cs</dc:creator>
      <dc:date>2026-11-13T09:36:50Z</dc:date>
    </item>
  </channel>
</rss>

