Adding a PostgreSQL Connection

Technical Documentation : Connectors : Adding a PostgreSQL Connection

Was this helpful?

Prerequisites

A user with sufficient permissions is required to establish a connection with PostgreSQL.
Zeenea traffic flows towards the database must be open.
In order to catalog datasets stored on PostgreSQL, Zeenea uses the JDBC API to extract metadata. The flow towards the PostgreSQL server must be open.

Target	Protocol	Usual Ports
PostgreSQL	JDBC	5432

Note: You can find a link to the configuration template in Zeenea Connector Downloads.

Supported Versions

The PostgreSQL connector was developed and tested with version 10.4. It is compatible with version 9.5 and later. It is also compatible with the PolarDB versions of the Alibaba Cloud service as well as with the RDS and Aurora versions of the Amazon Cloud service.

Installing the Plugin

From version 54 of the scanner, the PostgreSQL connector is presented as a plugin.

It can be downloaded here and requires a scanner version 64: Zeenea Connector Downloads

For more information on how to install a plugin, please refer to the following article: Installing and Configuring Connectors as a Plugin.

Declaring the Connection

Creating and configuring connectors is done through a dedicated configuration file located in the /connections folder of the relevant scanner. The scanner frequently checks for any change and resynchronises automatically.

Read more: Managing Connections

In order to establish a connection with a PostgreSQL instance, fill out the following parameters in the dedicated file:

Parameter	Expected value
name	The name that will be displayed to catalog users for this connection.
code	The unique identifier of the connection on the Zeenea platform. Once registered on the platform, this code must not be modified or the connection will be considered as new and the old one removed from the scanner.
connector_id	The type of connector to be used for the connection. Here, the value must be PgSql and this value must not be modified.
connection.url	Database address (example: jdbc:postgresql://postgresql.example.com:5432/database)
connection.username	Username
connection.password	User password
lineage.view.enabled	Set to true to activate the lineage feature. Default value false.

User Permissions

In order to collect metadata, the running user's permissions must allow them to access and read databases that need cataloging.

Here, the user must have read access to objects from the pg_catalog schema.

If the data profiling feature was enabled, the user must have read access on impacted tables. Otherwise, this permission is not necessary.

Data Extraction

To extract information, the connector runs requests on the following views from the pg_catalog schema:

pg_class
pg_namespace
pg_description
pg_attribute
pg_type

Collected Metadata

Inventory

Will collect the list of tables and views accessible by the user.

Lineage

From version 56 of the plugin, the connector has the lineage feature on the views. This feature allows you to automatically recreate the lineage in your catalog of the tables that were used to build the view.

Dataset

A dataset can be a table or a view.

Name
Source Description
Technical Data:
- Catalog: Source catalog
- Schema: Source schema
- Table: table name
- Type:
  - table
  - view
  - materialized view
  - index
  - sequence
  - foreign table
  - TOAST table
  - composite type
  - partitioned table
  - partitioned index

Field

Dataset field.

Name
Source Description
Type
Can be null: Depending on field settings
Multivalued: Not supported. Default value false.
Primary Key: Depending on the "Primary Key" field attribute
Technical Data:
- Technical Name
- Native type: field native type

Data Process

A data process represents the request to build a view.

Name: CREATEVIEW "view-name"

Data Profiling

Important: The Data Profiling feature, which can be enabled on this connection, allows Explorers to better understand the type of data stored in each field. This feature, which can be activated in the Scanner, runs by default on a weekly schedule, every Saturday. However, depending on the number of fields for which you enable this feature, the calculation can quickly become costly. Before enabling it, ensure that the estimated impact of this feature is acceptable and that the default frequency is appropriate.

The statistical profiles feature, also known as Data Profiling, is available for this connector. The impact of this feature must be evaluated before activating it on any of your connections. For more information about the resulting statistics, see Data Profiling.

To activate this feature, read access to the target tables is required. For PostgreSQL technologies, the connector executes the following request to get a data sample:

SELECT COUNT(*) AS result FROM tableName

The request above defines the number of rows in the table tableName.

SELECT
field1, field2
FROM tableName
TABLESAMPLE BERNOULLI (linesPercentage)

The request above collects a data sample for each field where the feature is activated through the studio (field1, field2). The limit is 10.000 lines (linesPercentage parameter) deduced from a calculation with the number of rows set in the previous request.

These requests will be executed, whether manually, in case of user action directly on the admin portal, or periodically according to the parameter collect-fingerprint from the application.conf file, as described in Zeenea Scanner Setup.

Unique Identifier Keys

Each object in the catalog is associated with a unique identifier key. When the object is imported from an external system, the key is generated and provided by the connector.

For more information about identifier keys, see Identification Keys.

Object	Identifier Key	Description
Dataset	code/schema/dataset name	- code: Unique identifier of the connection noted in the configuration file. - schema: Dataset schema - dataset name
Field	code/schema/dataset name/field name	- code: Unique identifier of the connection noted in the configuration file. - schema: Dataset schema - dataset name - field name

Last modified date: 11/28/2025