DB - PostgreSQL
Review the PostgreSQL Integration Guide.
Overview
PostgreSQL integration enables an Edge System to connect with a PostgreSQL database.
Supported Communication
- Outbound (Edge to Database) - Yes
- Inbound (Database to Edge) - No
Configurations
Variable | Detail | Required |
|---|---|---|
Name | Enter name for the connector | Yes |
Hostname | IP Address or Hostname of PostgreSQL Server (Must be reachable from the Edge system) | Yes |
Port | PostgreSQL Server port | Yes |
Username | User name | Yes |
Password | User password | Yes |
Database | Database name | Yes |
Table | Table name | Yes |
Show Mapping | Data from a predefined table could be mapped into a custom one. Example: {"from": "to"} where "from" is a column from predefined table, and "to" is a column from destination table. See Work with Tables in SQL Connectors (Create Table and Show Mapping) to learn more. | No |
Create table | If selected and table doesn't exist, the table is created with the necessary format. See Work with Tables in SQL Connectors (Create Table and Show Mapping) to learn more. | No |
Commit timeout | Transaction commit timeout (ms) | No |
Max transaction size | Maximum number of messages before a transaction is committed regardless of timeout | No |
Bulk insert count | To enable this option, enter the number of messages to group together and send as one bulk insert statement. Enabling this option can improve how quickly data is processed when dealing with high volumes of tags. Available for Manufacturing Connect Edge version 3.11.1 and later. | No |
Throttling limit | Set a limit on the number of outbound messages per second. If sending data to a server that has restrictions on the rate of incoming messages, this ensures that no messages are lost. | No |
Queue mode | Select the sequence of data transfer: FIFO or LIFO. Selecting FIFO (First In First Out) will send the earliest message first. Selecting LIFO (Last In First Out) will send the latest message first. | No |
Persistent storage | If enabled, messages in the outbound queue are stored on disk. If there are interruptions in connection or power loss, messages will be retained and eventually sent when the connection is restored. | No |
Compatibility Validation
This information is just for reference. More products and versions may be supported.
Product | Version |
|---|---|
PostgreSQL | 12 |