DB - PostgreSQL SSL

review the postgresql ssl integration guide docid\ ys02jg4xmddc96bdyiabv overview postgresql ssl integration enables an edge system to connect with a postgresql database using ssl authentication supported communication outbound (edge to database) yes inbound (database to edge) no configurations variable detail required name enter a name for the connector yes hostname ip address or hostname of the postgresql server (must be reachable from the edge system) yes port postgresql server port yes ssl mode ssl mode one of "require", "verify ca", "verify full" yes ca certificate ssl ca certificate no certificate ssl certificate no private key ssl private key no username user name (can be empty) no password user password (can be empty) no 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) docid\ arn eb7jkou2tcnsnyqnw to learn more 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) docid\ arn eb7jkou2tcnsnyqnw 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 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 note when the create table checkbox is not selected, the table format (columns) that you will create must still adhere to the following format create table if not exists "table name" ( id bigserial not null, record uuid uuid not null, arrived at timestamp with time zone not null, device id varchar(64) null, register id varchar(64) null, tag name varchar(64) null, datatype varchar(32) null, value varchar null, success boolean null, primary key (id) );