> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cube.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Postgres

> Supply PostgreSQL host, database name, credentials, and optional SSL or pool settings to connect Cube as a client.

## Prerequisites

* The hostname for the [Postgres][postgres] database server
* The username/password for the [Postgres][postgres] database server
* The name of the database to use within the [Postgres][postgres] database
  server

## Setup

### Manual

Add the following to a `.env` file in your Cube project:

```dotenv theme={"dark"}
CUBEJS_DB_TYPE=postgres
CUBEJS_DB_HOST=my.postgres.host
CUBEJS_DB_NAME=my_postgres_database
CUBEJS_DB_USER=postgres_user
CUBEJS_DB_PASS=**********
```

## Environment Variables

| Environment Variable                                                                      | Description                                                                        | Possible Values           | Required |
| ----------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- | ------------------------- | :------: |
| [`CUBEJS_DB_HOST`](/reference/configuration/environment-variables#cubejs_db_host)         | The host URL for a database                                                        | A valid database host URL |     ✅    |
| [`CUBEJS_DB_PORT`](/reference/configuration/environment-variables#cubejs_db_port)         | The port for the database connection                                               | A valid port number       |     ❌    |
| [`CUBEJS_DB_NAME`](/reference/configuration/environment-variables#cubejs_db_name)         | The name of the database to connect to                                             | A valid database name     |     ✅    |
| [`CUBEJS_DB_USER`](/reference/configuration/environment-variables#cubejs_db_user)         | The username used to connect to the database                                       | A valid database username |     ✅    |
| [`CUBEJS_DB_PASS`](/reference/configuration/environment-variables#cubejs_db_pass)         | The password used to connect to the database                                       | A valid database password |     ✅    |
| [`CUBEJS_DB_SSL`](/reference/configuration/environment-variables#cubejs_db_ssl)           | If `true`, enables SSL encryption for database connections from Cube               | `true`, `false`           |     ❌    |
| [`CUBEJS_DB_MAX_POOL`](/reference/configuration/environment-variables#cubejs_db_max_pool) | The maximum number of concurrent database connections to pool. Default is `8`      | A valid number            |     ❌    |
| [`CUBEJS_CONCURRENCY`](/reference/configuration/environment-variables#cubejs_concurrency) | The number of [concurrent queries][ref-data-source-concurrency] to the data source | A valid number            |     ❌    |

[ref-data-source-concurrency]: /admin/connect-to-data/concurrency#data-source-concurrency

## Pre-Aggregation Feature Support

### count\_distinct\_approx

Measures of type
[`count_distinct_approx`][ref-schema-ref-types-formats-countdistinctapprox] can
only be used in pre-aggregations when using the [Postgres HLL
extension][gh-postgres-hll] with Postgres as a source database.

## Pre-Aggregation Build Strategies

<Info>
  To learn more about pre-aggregation build strategies, [head
  here][ref-caching-using-preaggs-build-strats].
</Info>

| Feature       | Works with read-only mode? | Is default? |
| ------------- | :------------------------: | :---------: |
| Batching      |              ✅             |      ✅      |
| Export Bucket |              -             |      -      |

By default, Postgres uses [batching][self-preaggs-batching] to build
pre-aggregations.

### Batching

No extra configuration is required to configure batching for Postgres.

### Export Bucket

Postgres does not support export buckets.

## SSL

To enable SSL-encrypted connections between Cube and Postgres, set the
[`CUBEJS_DB_SSL`](/reference/configuration/environment-variables#cubejs_db_ssl) environment variable to `true`. For more information on how to
configure custom certificates, please check out [Enable SSL Connections to the
Database][ref-recipe-enable-ssl].

## Additional Configuration

### AWS RDS

Use `CUBEJS_DB_SSL=true` to enable SSL if you have SSL enabled for your RDS
cluster. Download the new certificate [here][aws-rds-pem], and provide the
contents of the downloaded file to [`CUBEJS_DB_SSL_CA`](/reference/configuration/environment-variables#cubejs_db_ssl_ca). All other SSL-related
environment variables can be left unset. See [the SSL section][self-ssl] for
more details. More info on AWS RDS SSL can be found [here][aws-docs-rds-ssl].

### Google Cloud SQL

You can connect to an SSL-enabled MySQL database by setting [`CUBEJS_DB_SSL`](/reference/configuration/environment-variables#cubejs_db_ssl) to
`true`. You may also need to set [`CUBEJS_DB_SSL_SERVERNAME`](/reference/configuration/environment-variables#cubejs_db_ssl_servername), depending on how
you are [connecting to Cloud SQL][gcp-docs-sql-connect].

### Heroku

Unless you're using a Private or Shield Heroku Postgres database, Heroku
Postgres does not currently support verifiable certificates. [Here is the
description of the issue from Heroku][heroku-postgres-issue].

As a workaround, you can set `rejectUnauthorized` option to `false` in the Cube
Postgres driver:

```javascript theme={"dark"}
const PostgresDriver = require("@cubejs-backend/postgres-driver")
module.exports = {
  driverFactory: () =>
    new PostgresDriver({
      ssl: {
        rejectUnauthorized: false
      }
    })
}
```

[aws-docs-rds-ssl]: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/UsingWithRDS.SSL.html

[aws-rds-pem]: https://s3.amazonaws.com/rds-downloads/rds-ca-2019-root.pem

[gcp-docs-sql-connect]: https://cloud.google.com/sql/docs/postgres/connect-functions#connect

[gh-postgres-hll]: https://github.com/citusdata/postgresql-hll

[heroku-postgres-issue]: https://help.heroku.com/3DELT3RK/why-can-t-my-third-party-utility-connect-to-heroku-postgres-with-ssl

[postgres]: https://www.postgresql.org/

[ref-caching-using-preaggs-build-strats]: /docs/pre-aggregations/using-pre-aggregations#pre-aggregation-build-strategies

[ref-recipe-enable-ssl]: /recipes/configuration/using-ssl-connections-to-data-source

[ref-schema-ref-types-formats-countdistinctapprox]: /reference/data-modeling/measures#type

[self-preaggs-batching]: #batching

[self-ssl]: #ssl