RDBMS

PostgreSQL

OvalEdge uses a JDBC driver to connect to the data source, which allows users to crawl and profile data objects (Tables, Table Columns, etc.) and build Lineage.

Overview

Connector Details

Connector Category

RDBMS System

OvalEdge Release Current Connector Version

6.3.4

Connectivity

[How OvalEdge connects to PostgreSQL]

JDBC

OvalEdge Releases Supported (Available from)

Release3.x Onwards

Connector Features

Crawling of Metadata Objects Supported  

Profiling

Supported

Profiling Methodologies

Full Profiling

Sample Profiling

**Data Types Not Supported 

"BYTEA", "JSONB", "LSEG", "POLYGON", "JSON", "BOX", "MACADDR", "LINE", "POINT", "ARRAY", "XID", "ANYARRAY", "OIDVECTOR", "INT2VECTOR", "BYTEA", "TID", "PG_LSN", "USER-DEFINED", "UUID", "HSTORE", "INT4RANGE", "INT8RANGE", "NUMRANGE", "TSRANGE", "TSTZRANGE", "DATERANGE"

Query Sheet

Supported

Data Preview

Supported

Lineage 

Supported

Lineage Levels Supported

Table Lineage

Column Lineage

Auto Lineage Sources

Stored Procedures, Functions, Triggers, Views, SQL queries (from Query Sheet)

Authentication via Credential Manager

Supported

Data Quality

Supported

DAM (Data Access Management)

Not Supported

Bridge

Supported 

Getting Ready to Establish a Connection

Prerequisites

The following are the prerequisites required for establishing a connection: 

Whitelisting Ports

Ensure the inbound port “5432” is whitelisted for OvalEdge to connect to the PostgreSQL database.

Service Account User Permissions

Important: We recommend having a separate service account to establish a connection from OvalEdge to the data source with minimal permissions.

Operations Minimum Permissions
Connection Validation SELECT
Crawl Tables and Views SELECT
Profile Schemas, Tables SELECT
Lineage Building SELECT
Relationships References
View Source Code OWNER of the view

Setup a Connection

Important: You must have the Connector Creator role to set up a connection in OvalEdge.

  1. Log into OvalEdge, go to Administration > Connectors, click + (New Connector), search for PostgreSQL, and complete the specific parameters.

    Note: Fields marked with an asterisk (*) are mandatory for establishing a connection.

    Field Name

    Description

    Connector Type

    By default, "PostgreSQL" is displayed as the selected connector type.

    Connector Settings

    Credential Manager*

    Select the desired credentials manager from the dropdown list. Relevant parameters will be displayed based on your selection.

    Supported Credential Managers:

    • OE Credential Manager
    • HashiCorp Vault
    • AWS Secrets Manager
    • Azure Key Vault

    License Add Ons

    OvalEdge connectors have a default license add-on for data crawling and profiling.

    • Select the checkbox for Auto Lineage Add-On to build data lineage automatically.
    • Select the checkbox for Data Quality Add-On to identify data quality issues using data quality rules and anomaly detection.

    Connector Name*

    Enter a unique name for the PostgreSQL connection.             

    (Example: "PostgreSQL_Prod").

    Connector Environment

    Select the environment (Example: PROD, STG) configured for the connector.

    Server*

    Enter the PostgreSQL database Server name or IP address (Example: PostgreSQL.example.com or 192.168.1.10).

    Port*

    By default, the port number for the PostgreSQL database "5432" is auto-populated. If necessary, you can change this to a different port number.

    Database*

    Enter the database name to which the service account user has access within the PostgreSQL server.

    Driver*

    By default, the PostgreSQL driver details (Example: org.postgresql.Driver) are auto-populated.

    OvalEdge artifacts include the required drivers for supported databases.

    Username*

    Enter the service account username set up to access the PostgreSQL database (Example: "oesauser").

    Password*

    Enter the password associated with the service account user (Example: "password").

    Connection String

    Configure the connection string for the PostgreSQL database:

    • Automatic Mode: The system generates a connection string based on the provided credentials.
      • Example (PostgreSQL): 

    jdbc:postgresql://{server}:5432/{sid}

    • Manual Mode: Manually enter a valid connection string by enabling the toggle.
      • Example (PostgreSQL): 

    jdbc:postgresql://{server}:{port}/{database}?ssl=true&sslmode=require

    Replace placeholders with actual database details.

    {sid} refers to Database Name.

    Default Governance Roles

    Default Governance Roles*

    Select the appropriate users or teams for each governance role from the dropdown list. All users and teams configured in OvalEdge Security are displayed for selection.

    Admin Roles

    Admin Roles*

    Select one or more users from the dropdown list for Integration Admin and Security and Governance Admin. All users configured in OvalEdge Security are available for selection.

    No Of Archive Objects*

    It indicates the number of recent metadata changes to a dataset at the source. By default, it is off. You can enable it by toggling the Archive button and specifying the number of objects to archive.

    Example: Setting it to 4 retrieves the last four changes, shown in the 'version' column of the 'Metadata Changes' module.

    Bridge

    Select Bridge*

    If applicable, select the bridge from the drop-down list.

    The drop-down list displays all active bridges configured in OvalEdge. These bridges enable communication between data sources and OvalEdge without altering firewall rules.

  2. After entering all connection details, you can perform the following actions:
    1. Click Validate to verify the connection.
    2. Click Save to store the connection for future use.
    3. Click Save & Configure to apply additional settings before saving.

Connectivity Troubleshooting

If incorrect parameters are provided, you may encounter error messages. To resolve these issues, ensure all input is correct. If problems persist, contact your assigned OvalEdge support team.

S.No.

Error Description

Resolution

1

Error while validating connection: Exception occured while validating the PostgreSql Connection : Failed to obtain JDBC Connection; nested exception is org.postgresql.util.PSQLException: FATAL: password authentication failed for user "postgres"

  • Verify Credentials
  • Check Database Configuration
  • Ensure the PostgreSQL Server is Running

2

Error while validating connection: Exception occured while validating the PostgreSql Connection : Failed to obtain JDBC Connection; nested exception is org.postgresql.util.PSQLException: FATAL: database "ovaledge" does not exist

  • Verify Database Name
  • Create the Database (If Missing)
  • Check User Permissions
  • Restart PostgreSQL (If Needed)

3

Error while validating connection: Exception occured while validating the PostgreSql Connection : Failed to obtain JDBC Connection; nested exception is org.postgresql.util.PSQLException: Connection to 192.168.1.193:5436 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.

  • Verify Hostname and Port
  • Ensure PostgreSQL is Running
  • Enable TCP/IP Connections
  • Check Firewall and Network Rules

4

Error while validating connection: Exception occured while validating the PostgreSql Connection : Failed to obtain JDBC Connection; nested exception is org.postgresql.util.PSQLException: The connection attempt failed.

  • Verify Connection Details
  • Check if PostgreSQL is Running
  • Ensure the PostgreSQL Server is Listening on the Correct Port
  • Check Network Connectivity
  • Check PostgreSQL Logs for Errors

Manage Connector Operations

Configure Settings for Connector Operations

The PostgreSQL connector offers various settings to customize data crawling, profiling, and access. These include:

  • Crawler: Configure data that needs to be extracted.
  • Profiler: Customize data profiling rules and methods.
  • Query Policies: Define rules for executing queries based on roles. 
  • Access Instructions: Specify how data can be accessed as a note. 
  • Business Glossary Settings: Manage term associations at the connector level.
  • Others: Configure notification recipients for metadata changes.

Crawl/Profile

Important: You must have the Integration Admin role in OvalEdge for crawl/profile operations.

Crawl and Profile operations enable you to select one or more schemas from a list of all available schemas within a specific database. This allows you to customize the crawling and profiling operations selection according to your requirements. Furthermore, it provides the option to schedule crawling and profiling and enable anomaly detection to identify any irregularities in the data objects.

Other Operations

The Connectors page in OvalEdge provides a centralized view of all configured connectors, including their health status. You can view, edit, validate, build lineage, and delete connectors using the Nine Dots menu.

Managing connectors includes:

  • Connectors Health: Displays performance with a green (active) or red (inactive) icon, helping monitor data flow and address issues early.
  • Viewing: Shows connector details (e.g., Databases, Tables, Table Columns, and Codes) via the View icon.

Nine Dots Menu Options:

  • Edit Connector: Update and revalidate the data source.
  • Validate Connector: Check the connection's integrity.
  • Settings: Modify connector settings.
  • Build Lineage: Automatically build data lineage using SQL logs and source code parsing.
  • Delete Connector: Remove connectors or schemas with confirmation.

                                                 Copyright © 2025, OvalEdge LLC, Peachtree Corners GA USA