<?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: Is it possible to have Lakebase Postgres as a compute option for an AI/BI Dashboard? in Lakebase Discussions</title>
    <link>https://community.databricks.com/t5/lakebase-discussions/is-it-possible-to-have-lakebase-postgres-as-a-compute-option-for/m-p/148018#M6</link>
    <description>&lt;P&gt;You can register Lakebase as read-only foreign catalog. In this case both computes will be used ( Sql end point and Lakebase). Doing lots of entitlement filtering via ABAC policies when dashboard being used can be tricky. Pre aggravated MV can be a choice.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Below are my questions to understand the problem better.&lt;/P&gt;&lt;P&gt;What is the expected peak number of concurrent users?&lt;/P&gt;&lt;P&gt;Is the aggregation level safe with ABAC filtering? Assuming you have row based filtering.&lt;/P&gt;&lt;P&gt;What attributes drive ABAC policies (region, business unit, etc.)?&lt;/P&gt;&lt;P&gt;Will ABAC require runtime joins to entitlement tables?&lt;/P&gt;&lt;P&gt;Which compute will serve users, and is autoscaling enabled?&lt;/P&gt;</description>
    <pubDate>Wed, 11 Feb 2026 09:29:06 GMT</pubDate>
    <dc:creator>KartikBhatnagar</dc:creator>
    <dc:date>2026-02-11T09:29:06Z</dc:date>
    <item>
      <title>Is it possible to have Lakebase Postgres as a compute option for an AI/BI Dashboard?</title>
      <link>https://community.databricks.com/t5/lakebase-discussions/is-it-possible-to-have-lakebase-postgres-as-a-compute-option-for/m-p/147954#M4</link>
      <description>&lt;P&gt;Can dashboards be powered by Lakebase Postgres?&lt;/P&gt;&lt;P&gt;I noticed I can select it in the 'Queries' editor, but it doesn't seem to be an option for dashboards, which currently only shows SQL Warehouse and Serverless.&lt;/P&gt;&lt;P&gt;Any way around this?&lt;BR /&gt;&lt;EM&gt;Our aim is to support a lot of concurrent users that fetch a pre-aggregated dataset, on top of which Unity Catalog ABAC policies are applied at runtime.&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 10 Feb 2026 20:46:35 GMT</pubDate>
      <guid>https://community.databricks.com/t5/lakebase-discussions/is-it-possible-to-have-lakebase-postgres-as-a-compute-option-for/m-p/147954#M4</guid>
      <dc:creator>ttsaklanos</dc:creator>
      <dc:date>2026-02-10T20:46:35Z</dc:date>
    </item>
    <item>
      <title>Re: Is it possible to have Lakebase Postgres as a compute option for an AI/BI Dashboard?</title>
      <link>https://community.databricks.com/t5/lakebase-discussions/is-it-possible-to-have-lakebase-postgres-as-a-compute-option-for/m-p/147957#M5</link>
      <description>&lt;P&gt;Greetings&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/215585"&gt;@ttsaklanos&lt;/a&gt;&amp;nbsp;, &lt;SPAN&gt;Quick clarification up front: dashboards don’t run directly on Lakebase Postgres. They always execute on a Databricks SQL warehouse (Pro or Serverless). Today, there isn’t a way to select “Lakebase Postgres” itself as the dashboard compute.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Hope this helps, Louis.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 10 Feb 2026 21:34:05 GMT</pubDate>
      <guid>https://community.databricks.com/t5/lakebase-discussions/is-it-possible-to-have-lakebase-postgres-as-a-compute-option-for/m-p/147957#M5</guid>
      <dc:creator>Louis_Frolio</dc:creator>
      <dc:date>2026-02-10T21:34:05Z</dc:date>
    </item>
    <item>
      <title>Re: Is it possible to have Lakebase Postgres as a compute option for an AI/BI Dashboard?</title>
      <link>https://community.databricks.com/t5/lakebase-discussions/is-it-possible-to-have-lakebase-postgres-as-a-compute-option-for/m-p/148018#M6</link>
      <description>&lt;P&gt;You can register Lakebase as read-only foreign catalog. In this case both computes will be used ( Sql end point and Lakebase). Doing lots of entitlement filtering via ABAC policies when dashboard being used can be tricky. Pre aggravated MV can be a choice.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Below are my questions to understand the problem better.&lt;/P&gt;&lt;P&gt;What is the expected peak number of concurrent users?&lt;/P&gt;&lt;P&gt;Is the aggregation level safe with ABAC filtering? Assuming you have row based filtering.&lt;/P&gt;&lt;P&gt;What attributes drive ABAC policies (region, business unit, etc.)?&lt;/P&gt;&lt;P&gt;Will ABAC require runtime joins to entitlement tables?&lt;/P&gt;&lt;P&gt;Which compute will serve users, and is autoscaling enabled?&lt;/P&gt;</description>
      <pubDate>Wed, 11 Feb 2026 09:29:06 GMT</pubDate>
      <guid>https://community.databricks.com/t5/lakebase-discussions/is-it-possible-to-have-lakebase-postgres-as-a-compute-option-for/m-p/148018#M6</guid>
      <dc:creator>KartikBhatnagar</dc:creator>
      <dc:date>2026-02-11T09:29:06Z</dc:date>
    </item>
  </channel>
</rss>

