New in Looker 7.10, Looker can use connection pools on PostgreSQL to improve query performance.
Dialects Using These Instructions
PostgreSQL, Google Cloud PostgreSQL, and Microsoft Azure PostgreSQL share database setup requirements as described on this page. However, for PostgreSQL on Heroku please see our PostgreSQL on Heroku documentation page.
Encrypting Network Traffic
Looker strongly recommends encrypting network traffic between the Looker application and your database. Consider one of the options described on the Enabling secure database access documentation page.
If you’re interested in using SSL encryption, see the PostgreSQL documentation.
Users and Security
some_password_here to a unique, secure password:
If you’re using a schema other than
public, run this command to grant usage permissions to Looker:
To make sure that future tables you add to the public schema are also available to the Looker user, run these commands:
Temp Schema Setup
Create a schema owned by the Looker user:
Postgres on Amazon RDS
Create a scratch schema:
Change the ownership of the scratch schema to the Looker user:
For PostgreSQL persistent derived tables to work, you must not be using Looker on top of a “hot swap” streaming replication database. You must be able to write to the database from outside the application.
Finally, you should set an appropriate
search_path, which Looker’s SQL Runner uses to retrieve certain metadata from your database. Assuming you have created a user called
looker, and a temp schema called
looker_scratch, the command is:
For Looker to support some features, your database dialect must also support them.
In Looker 21.6, PostgreSQL supports the following Looker features:
In Looker 21.6, Google Cloud PostgreSQL supports the following Looker features:
In Looker 21.6, Microsoft Azure PostgreSQL supports the following Looker features:
After completing the database configuration, you can connect to the database from Looker using these directions.