PostgreSQL

To bring your PostgreSQL data into Neo, all you need is a few details about your database and how you want to authenticate. This guide helps you set everything up smoothly.

Getting Started

To connect to a PostgreSQL database, you’ll need:

  • Basic connection details like host, port, database, and schema

  • One of two authentication options:

    • Standard Authentication (user & password)

    • SSL Authentication (for secure, certificate-based access)

Connection Details

Here’s what each field means and how to fill it out:

1. Name

Pick a unique name for this PostgreSQL source.

This is how you’ll recognize the source later when managing multiple sources.

Example:

  • postgres-prod

  • analytics-db

  • finance-postgres-eu

This name must be unique across all your sources.

2. Host

Provide the hostname or IP address of your PostgreSQL server.

Example: postgres.internal.mycompany.com or 192.168.0.25

3. Port

The port used to connect to PostgreSQL.

Unless changed by your admin, the default is 5432.

4. Database

Enter the name of the PostgreSQL database you want to connect to.

Example: customer_data, inventory

5. Schema

Specify the schema within your database where your tables reside.

Example: public, sales, metrics

Authentication Options

You can choose one of two authentication methods depending on how your PostgreSQL server is secured:

Option 1: Standard Authentication

Use this if your database uses a username and password for login.

You’ll need:

User:

Your PostgreSQL username.

Example: readonly_user

Password:

The matching password.

This will be securely masked in the UI.

Option 2: SSL Authentication

This option is best for production or secure environments using SSL certificates.

You’ll need:

User:

Your PostgreSQL login name.

Password:

The user’s password.

SSL Root Certificate (ssl_ca):

This is the certificate that verifies the PostgreSQL server (typically ca.crt).

SSL Client Certificate (ssl_cert):

This is the certificate that identifies your client (typically client.crt).

SSL Client Key (ssl_key):

This is your private key file used to establish trust with the server (typically client.key).

Make sure your certificates are in PEM format and correctly mapped to the database user.

Still have Questions?

We’ll be happy to help you with any questions you might have! Send us an email at info@datachannel.co.

Subscribe to our Newsletter for latest updates at DataChannel.