PostgreSQL

Connect Querri to your PostgreSQL database to analyze data using natural language. Once connected, simply ask questions—Querri handles all the SQL for you.

Overview

The PostgreSQL connector supports:

• PostgreSQL 9.6+: All modern PostgreSQL versions
• AWS RDS PostgreSQL: Managed PostgreSQL on AWS
• Azure Database for PostgreSQL: Managed PostgreSQL on Azure
• Google Cloud SQL for PostgreSQL: Managed PostgreSQL on GCP
• Heroku Postgres: Heroku’s managed PostgreSQL

Setup

Prerequisites

• PostgreSQL database server
• Database credentials with appropriate permissions
• Network access to the database

IP Whitelisting

Important: For cloud-hosted databases or databases behind firewalls, whitelist the following IP address:

18.189.33.77

This is Querri’s outbound IP address. Add this to your database firewall rules or security group.

Creating the Connector

1. Navigate to Connectors

   • Go to Settings → Connectors
   • Click “Add Connector”

2. Select PostgreSQL

   • Choose “PostgreSQL” from the database connectors

3. Configure Connection

Host: your-database-host.com
Port: 5432 (default PostgreSQL port)
Database: your_database_name
Username: your_username
Password: your_password

Optional Settings:

• SSL Mode:
  • require - Always use SSL (recommended)
  • prefer - Use SSL if available
  • disable - Don’t use SSL
• Schema: Default is public
• Connection Timeout: Default is 30 seconds

4. Test Connection

   • Click “Test Connection” to verify
   • If successful, click “Save”

5. Start Analyzing

   • Tables appear in your Library
   • Create a project from any table
   • Ask questions in natural language

Network Configuration

AWS RDS Security Groups

Add inbound rule:

Type: PostgreSQL
Protocol: TCP
Port: 5432
Source: 18.189.33.77/32
Description: Querri Access

Azure PostgreSQL Firewall

Add firewall rule:

Rule Name: Querri
Start IP: 18.189.33.77
End IP: 18.189.33.77

Google Cloud SQL

Add authorized network:

Name: Querri
Network: 18.189.33.77/32

Heroku Postgres

Heroku Postgres allows connections from any IP by default. No configuration needed.

Database User Setup

Read-Only User (Recommended)

Create a dedicated read-only user for Querri:

-- Create user
CREATE USER querri_readonly WITH PASSWORD 'secure_password_here';

-- Grant connect permission
GRANT CONNECT ON DATABASE your_database TO querri_readonly;

-- Grant schema usage
GRANT USAGE ON SCHEMA public TO querri_readonly;

-- Grant select on all tables
GRANT SELECT ON ALL TABLES IN SCHEMA public TO querri_readonly;

-- Grant select on future tables
ALTER DEFAULT PRIVILEGES IN SCHEMA public
GRANT SELECT ON TABLES TO querri_readonly;

Restricting Access to Specific Tables

For tighter security, grant access only to specific tables or views:

-- Grant access to specific tables only
GRANT SELECT ON orders, customers, products TO querri_readonly;

-- Or grant access only to an analytics schema
GRANT USAGE ON SCHEMA analytics TO querri_readonly;
GRANT SELECT ON ALL TABLES IN SCHEMA analytics TO querri_readonly;

See Database Best Practices for detailed guidance on creating analytics views and restricting access.

Troubleshooting

Connection Timeout

Problem: Cannot connect to database

Solutions:

1. Verify IP 18.189.33.77 is whitelisted
2. Check database host and port are correct
3. Verify database is running and accessible
4. Check SSL mode settings
5. Verify network connectivity

Authentication Failed

Problem: Invalid credentials error

Solutions:

1. Double-check username and password
2. Verify user exists: SELECT * FROM pg_user WHERE usename = 'your_username';
3. Check user has connect permission
4. Verify database name is correct

Permission Denied

Problem: Permission denied on table/schema

Solutions:

1. Grant necessary permissions (see Database User Setup)
2. Verify schema name is correct
3. Check table ownership
4. Run: \dp table_name to see table permissions

SSL Connection Error

Problem: SSL connection failed

Solutions:

1. Try different SSL modes (prefer, require, disable)
2. Verify server SSL certificate is valid
3. Check PostgreSQL SSL configuration
4. For RDS, ensure SSL is enabled

Security Best Practices

Use Read-Only Credentials

Create dedicated read-only users for analytics:

• Prevents accidental data modification
• Limits potential security impact
• Easier to audit and monitor

Enable SSL

Always use SSL for production databases:

SSL Mode: require

Restrict Permissions

Grant only necessary permissions:

-- Only SELECT on specific tables
GRANT SELECT ON TABLE orders, customers TO querri_readonly;

-- Only specific columns (if needed)
GRANT SELECT (customer_id, email, created_at) ON customers TO querri_readonly;

Regular Audits

Monitor database access:

-- View active connections
SELECT * FROM pg_stat_activity
WHERE usename = 'querri_readonly';

PostgreSQL Versions

Tested and supported versions:

• PostgreSQL 16.x ✓
• PostgreSQL 15.x ✓
• PostgreSQL 14.x ✓
• PostgreSQL 13.x ✓
• PostgreSQL 12.x ✓
• PostgreSQL 11.x ✓ (limited support)
• PostgreSQL 10.x ✓ (limited support)
• PostgreSQL 9.6.x ✓ (limited support)

Next Steps

• Database Best Practices — Create analytics views and optimize for natural language queries
• Data Connectors Overview — See all available connectors
• Managing Connections — Edit and monitor your connectors