Starburst PostgreSQL connector#

The Starburst PostgreSQL connector is an extended version of the PostgreSQL Connector with configuration and usage identical.

The following improvements are included:


The additional features of the connector require a valid Starburst Enterprise Presto license, unless otherwise noted.


The connector includes a number of performance improvements, detailed in the following sections.

Table statistics#

This feature is available for free, and does not require a valid license.

PostgreSQL connector supports table and column statistics, as documented in Table Statistics. The statistics are collected by PostgreSQL and retrieved by the connector. To collect statistics for a table, execute the following statement in PostgreSQL.

ANALYZE table_schema.table_name;

Refer to PostgreSQL documentation for additional ANALYZE options.

The table and column statistics can be viewed in Presto using SHOW STATS and are used for Cost based optimizations.

Table statistics configuration properties#

Property Name




Enables table and column statistics.



Duration for which table and column statistics are cached.



Cache the fact that table statistics are not available.


Dynamic filtering#

Dynamic filtering is enabled by default. It causes the connector to wait for dynamic filtering to complete before starting a JDBC query.

You can disable dynamic filtering by setting the property dynamic-filtering.enabled in your catalog properties file to false.


The connector includes a number of security-related features, detailed in the following sections.

User impersonation#

The PostgreSQL connector supports user impersonation.

User impersonation can be enabled in the catalog file:


User impersonation in PostgreSQL connector is based on SET ROLE. For more details visit:

Kerberos authentication#

The PostgreSQL connector supports Kerberos-based authentication with the following configuration:


With this configuration the user, defined in the principal property, is used to connect to the database, and the related Kerberos service ticket is located in the example.keytab file.

Kerberos credential passthrough#

The PostgreSQL connector can be configured to pass through Kerberos credentials, received by Presto, to the PostgreSQL database.

Configure Kerberos and Presto, following the instructions in Kerberos credential passthrough.

Then configure the connector to pass through the credentials from the server to the database in your catalog properties file and ensure the Kerberos client configuration properties are in place on all nodes.


Now any database access via Presto is subject to the data access restrictions and permissions of the user supplied via Kerberos.

Password credential passthrough#

The connector supports password credential passthrough. This means that the data Presto accesses is the same as the data available to a user who has direct access to the data source.

To enable it, edit the catalog properties file to include the authentication type:


For more information about configurations and limitations, see Password credential passthrough.