How to Connect ParadeDB to Looker in PostgreSQL

Galaxy Glossary

How do I connect ParadeDB to Looker?

Create a PostgreSQL-compatible JDBC connection so Looker can query ParadeDB datasets.

Welcome to the Galaxy, Guardian!
You'll be receiving a confirmation email

Follow us on twitter :)

Oops! Something went wrong while submitting the form.

Description

Example H2

Example H3

Why link ParadeDB and Looker?

Connecting ParadeDB to Looker lets analysts build real-time dashboards on ParadeDB’s vector and relational data without ETL. ParadeDB speaks the PostgreSQL wire protocol, so Looker treats it as a standard Postgres database.

Which Looker settings are required?

In Admin → Connections choose Dialect PostgreSQL. Enter host, port, database, username, and password. ParadeDB usually listens on port 5432.

Do I need SSL?

Set SSL = require unless ParadeDB runs on the same private network. ParadeDB supports the standard sslmode parameters.

How do I format the JDBC string?

Looker builds the string from the form fields, but for reference it resolves to jdbc:postgresql://HOST:PORT/DATABASE?sslmode=require. ParadeDB requires no extra parameters.

Can I restrict Looker to read-only?

Create a dedicated ParadeDB role with SELECT privileges on reporting schemas. Deny INSERT/UPDATE/DELETE to prevent accidental writes.

SQL to create the role

CREATE ROLE looker_readonly LOGIN PASSWORD '•••';GRANT CONNECT ON DATABASE ecommerce TO looker_readonly;GRANT USAGE ON SCHEMA public TO looker_readonly;GRANT SELECT ON ALL TABLES IN SCHEMA public TO looker_readonly;ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT SELECT ON TABLES TO looker_readonly;

How do I test the connection?

Click Test These Settings in Looker. A green check confirms connectivity. Run a sample explore to verify query results.

Example: build a customer orders view

Create a LookML model sourcing the Customers, Orders, and OrderItems tables. Join on customer_id to visualize revenue per customer.

Best practices for production

Enable connection pooling in ParadeDB’s postgresql.conf for high-concurrency BI workloads. Monitor slow queries with pg_stat_statements and add indexes on join columns like Orders.customer_id.

What are common errors?

"FATAL: no pg_hba.conf entry" means ParadeDB’s pg_hba.conf blocks Looker’s IP; add a hostssl line. "password authentication failed" indicates a bad credential or wrong database.

Why How to Connect ParadeDB to Looker in PostgreSQL is important

How to Connect ParadeDB to Looker in PostgreSQL Example Usage


-- Verify Looker can read data
SELECT c.id,
       c.name,
       COUNT(o.id)            AS order_count,
       SUM(o.total_amount)    AS lifetime_value
FROM   Customers c
LEFT JOIN Orders o ON o.customer_id = c.id
GROUP BY c.id, c.name
ORDER BY lifetime_value DESC
LIMIT 10;

How to Connect ParadeDB to Looker in PostgreSQL Syntax


Looker Connection Form → PostgreSQL Dialect
------------------------------------------------
Host        : parade-db.company.internal
Port        : 5432
Database    : ecommerce
Username    : looker_readonly
Password    : ********
SSL         : require (maps to sslmode=require)
Connection  : jdbc:postgresql://parade-db.company.internal:5432/ecommerce?sslmode=require

Optional Parameters
-------------------
search_path : public, analytics
max_pool    : 5 (default)
timeout     : 120

ParadeDB Role Setup
-------------------
CREATE ROLE looker_readonly LOGIN PASSWORD 'ChangeMe';
GRANT CONNECT ON DATABASE ecommerce TO looker_readonly;
GRANT USAGE ON SCHEMA public TO looker_readonly;
GRANT SELECT ON ALL TABLES IN SCHEMA public TO looker_readonly;
ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT SELECT ON TABLES TO looker_readonly;

Common Mistakes

Using the "Other JDBC" dialect. Looker’s native PostgreSQL dialect already handles ParadeDB. Choosing Other disables advanced SQL features and causes date truncation errors.
Granting Looker superuser rights. Excessive privileges risk data corruption. Fix by creating a read-only role with SELECT on necessary schemas only.