Skip to main content

EDB Postgres Advanced Server

Overview​

The EDB Postgres Advanced Server destination lets you load data into an EDB Postgres Advanced Server database. This destination is Postgres-compatible and uses standard Postgres connection settings.

Prerequisites​

  • Network access from the platform to your EDB Postgres instance (VPC peering, allowlisted IPs, or equivalent).
  • A database and schema to load into.
  • A database user with permissions to create and write to tables in the target schema.

Authentication​

Authenticate using standard Postgres credentials:

  • Host
  • Port
  • Database
  • User
  • Password
  • (Optional) SSL/TLS settings, depending on your deployment requirements

Configuration​

Provide the following configuration fields when setting up the destination.

FieldTypeRequiredDescription
Hoststring✓Hostname or IP address of the EDB Postgres server.
Portnumber✓Port for the Postgres service (commonly 5432).
Databasestring✓Database name to connect to.
Userstring✓Username for the database connection.
Passwordstring✓Password for the database connection.
Schemastring✓Target schema where tables will be created/updated.
SSL modestringSSL/TLS behavior (for example, require, verify-ca, verify-full, depending on your environment).

Data loading behavior​

  • Data is loaded into tables in the configured schema.
  • Table creation and write behavior follows the platform’s standard Postgres-compatible destination semantics.

Hashing and normalization​

This destination does not currently expose field-level hashing controls in its configuration.

Data contract​

The destination writes records into relational tables in EDB Postgres. Column types and table structure are derived from the incoming records and the platform’s standard typing rules for Postgres-compatible destinations.

Streams​

This is a destination connector. It does not define source streams; it receives records from upstream models/streams and loads them into EDB Postgres tables.