Issues Connecting Metabase to Data Studio Using Postgres – Workaround Via BigQuery

·Sep 07, 2026 04:40 PM·

#BI Tools Hi Beautiful people, I have a really quick question... More like an Issue. I followed all docs to connect MD to Data Studio (Looker) and haven't been able to.. I tested the connection localy via DBeaver using the postgres and it worked perfectly, So as workarround I had to ingest the Data from MD to BigQuery and therefore connect it to Data Studio. Any Advice here??? Thanks so much

9 comments

· Sorted by Oldest

MotherDuck
APP
·
·
Greetings from The Hatchery! MotherDuck is closed Monday, September 7th in observance of Labor Day. Our on-call teams will still be monitoring for any urgent issues, so please don't hesitate to reach out if something comes up. We'll be back to our regular hours on Tuesday, September 8th. As always, we're grateful for the opportunity to partner with you.
👍1
Yahia M.
·
·
Hi John J., happy to take a look! Can you share what errors or issues you face when connecting the Looker instance to MotherDuck?
John J.
·
(edited)·
Yahia, thanks for responding ... Just keep loading forever ... also I was wondering if the postgres is meant to be connected to Looker and not Data Studio (Formally Looker Studio)
John J.
·
(edited)·
Here are some examples on DBeaver (Which connected easily) and Data Studio
Yahia M.
·
·
Thanks for sharing the screenshots! You're right that the Looker docs (here) don't cover Looker Studio, as they're different connectors. Two things worth changing:
1.
Enable SSL in the connector and upload the ISRG Root X1 certificate. Our Postgres endpoint accepts encrypted connections, and Looker Studio is quicker to connect this way (Google's guide).
2.
The empty table list is separate: Google's PostgreSQL connector only looks for tables in a schema named public, and MotherDuck keeps yours in main. The Custom Query tab gets around it, using the full path:
SELECT * FROM remote_flowers.main.<your_table>
Out of interest, do you need the table picker for browsing, or is one query per data source workable? If browsing matters there's a way to get that populated too, happy to share it.
John J.
·
·
Man thank you thank you so much, was create a public schema and move my tables there, took seconds using the certificate and the basic connection. I guess should be in the docs, or if it already is, then make a callout for un-aware people like me hahahah
Yahia M.
·
·
Glad it worked! Absolutely, I'll follow up with the team to update the docs, apologies for the friction here! 😅
1
Yahia M.
·
·
Docs are updated here! Let me know if you have any further questions!
❤️1
John J.
·
·
love it. thanks man. Really appreciate it!!
🙌1

MotherDuck
APP
·
·
Greetings from The Hatchery! MotherDuck is closed Monday, September 7th in observance of Labor Day. Our on-call teams will still be monitoring for any urgent issues, so please don't hesitate to reach out if something comes up. We'll be back to our regular hours on Tuesday, September 8th. As always, we're grateful for the opportunity to partner with you.
👍1
Yahia M.
·
·
Hi John J., happy to take a look! Can you share what errors or issues you face when connecting the Looker instance to MotherDuck?
John J.
·
(edited)·
Yahia, thanks for responding ... Just keep loading forever ... also I was wondering if the postgres is meant to be connected to Looker and not Data Studio (Formally Looker Studio)
John J.
·
(edited)·
Here are some examples on DBeaver (Which connected easily) and Data Studio
Yahia M.
·
·
Thanks for sharing the screenshots! You're right that the Looker docs (here) don't cover Looker Studio, as they're different connectors. Two things worth changing:
1.
Enable SSL in the connector and upload the ISRG Root X1 certificate. Our Postgres endpoint accepts encrypted connections, and Looker Studio is quicker to connect this way (Google's guide).
2.
The empty table list is separate: Google's PostgreSQL connector only looks for tables in a schema named public, and MotherDuck keeps yours in main. The Custom Query tab gets around it, using the full path:
SELECT * FROM remote_flowers.main.<your_table>
Out of interest, do you need the table picker for browsing, or is one query per data source workable? If browsing matters there's a way to get that populated too, happy to share it.
John J.
·
·
Man thank you thank you so much, was create a public schema and move my tables there, took seconds using the certificate and the basic connection. I guess should be in the docs, or if it already is, then make a callout for un-aware people like me hahahah
Yahia M.
·
·
Glad it worked! Absolutely, I'll follow up with the team to update the docs, apologies for the friction here! 😅
1
Yahia M.
·
·
Docs are updated here! Let me know if you have any further questions!
❤️1
John J.
·
·
love it. thanks man. Really appreciate it!!
🙌1