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.
This feature is available for free, and does not require a valid license.
The PostgreSQL connector supports table and column statistics to improve query processing performance based on the actual data in the data source.
The statistics are collected by PostgreSQL and retrieved by the connector.
To collect statistics for a table, execute the following statement in PostgreSQL.
Refer to PostgreSQL documentation for additional
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
Caching table projections#
The connectors supports table scan redirection to improve performance and reduce load on the data source.
The connector includes a number of security-related features, detailed in the following sections.
The PostgreSQL connector supports user impersonation.
User impersonation can be enabled in the catalog file:
User impersonation in PostgreSQL connector is based on
For more details visit: www.postgresql.org/docs.
The PostgreSQL connector supports Kerberos-based authentication with the following configuration:
postgresql.authentication.type=KERBEROS firstname.lastname@example.org kerberos.client.keytab=etc/kerberos/example.keytab kerberos.config=etc/kerberos/krb5.conf
With this configuration the user
email@example.com, defined in the
principal property, is used to connect to the database, and the related Kerberos
service ticket is located in the
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.
postgresql.authentication.type=KERBEROS_PASS_THROUGH http.authentication.krb5.config=/etc/krb5.conf http-server.authentication.krb5.service-name=exampleServiceName http-server.authentication.krb5.keytab=/path/to/Keytab/File
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.