TIBCO Scribe® Online Connector For PostgreSQL

The TIBCO Scribe® Online Connector for PostgreSQL allows you to easily integrate your PostgreSQL databases with other business systems such as ERP, CRM, and Marketing Automation. This Connector discovers tables, views, and columns. In addition, you can use native SQL queries to access, filter, and join your data.

Use the PostgreSQL Connector as a source or target Connection for Integration Solutions. This Connector is based on the Scribe.Connector.AdoNet library and CData PostgreSQL ADO.NET provider.

Use the TIBCO Scribe® Connector for PostgreSQL to:

Connector Specifications


Agent Types

On Premise X
Cloud X

Replication Services


Integration Services

Source X
Target X

Migration Services



Integration X
Request-Reply X

This Connector is available from the TIBCO Scribe® Online Marketplace. See Marketplace TIBCO Scribe® Certified Connectors for more information.

Supported Entities

Advanced considerations, such as customizing the SSL configuration, or connecting through a firewall or a proxy, are described in the Advanced Settings section of the CData documentation.

Setup Considerations

Selecting An Agent Type For PostgreSQL

Refer to TIBCO Scribe® Online Agents for information on available Agent types and how to select the best Agent for your Solution.

Connecting To PostgreSQL

Note: Best practice is to create Connections with credentials that limit permissions in the target system, following the principle of least privilege. Using Administrator level credentials in a Connection provides Administrator level access to the target system for TIBCO Scribe® Online users. Depending on the entities supported, a TIBCO Scribe® Online user could alter user accounts in the target system.

  1. Select More > Connections from the menu.
  2. From the Connections page select Add to open the Add a New Connection dialog.
  3. Select the Connector from the drop-down list in the Connection Type field, and then enter the following information for this Connection:
    • Name — This can be any meaningful name, up to 25 characters.
    • Alias — An alias for this Connection name. The alias is generated from the Connection name, and can be up to 25 characters. The Connection alias can include letters, numbers, and underscores. Spaces and special characters are not accepted. You can change the alias. For more information, see Connection Alias.
    • Server — IP address or URL of the target PostgreSQL server instance. Requires a valid IPv4 IP or Url address.
    • PortPostgreSQL server port number, which must be in the 1023 to 65535 range. Default value is 5432.
    • Database — Name of the database to which you want to connect.
    • Username — User name for this PostgreSQL database instance.
    • Password — Password for this Username. PostgreSQL databases do not require a password.
    • Additional Parameters — Optional field where you can specify one or more connection string parameters. See the Connection String Options section of the CData documentation for a list of parameters that can be used and their default values. Note that in some cases the CData PostgreSQL ADO.NET provider does not fully support all of the possible parameters.

      Syntax for the Additional Parameters field is as follows:

      • Schema name is required for tables and views in the format schemaname.tablename or schemaname.viewname. For example: Tables=scribe.mhs_test;Views=scribe.mhs_list;Timeout=300;
      • All blank characters, except those within a value or within quotation marks, are ignored
      • Preceding and trailing spaces are ignored unless enclosed in single or double quotes, such as Keyword=" value"
      • Semicolons (;) within a value must be delimited by quotation marks
      • Use a single quote (') if the value begins with a double quote (")
      • Use a double quote (") if the value begins with a single quote (')
      • Parameters are case-insensitive
      • If a KEYWORD=VALUE pair occurs more than once in the connection string, the value associated with the last occurrence is used
      • If a keyword contains an equal sign (=), it must be preceded by an additional equal sign to indicate that the equal sign is part of the keyword
      • Parameters that are handled by other fields or default settings in the Connection dialog are ignored if used in the Additional Parameters field, including: 
        • Server
        • Port
        • User
        • Password
        • Logfile — To enable logging enter a value for the verbosity parameter in the Additional Parameters field. The default log file size is a maximum of 10MB. When the log file reaches 10MB a new log file is started, up to a maximum of five files. Once there are five files, the oldest file is deleted as needed. Any CData log files generated by this setting are stored in the default TIBCO Scribe® Online Agent Logs directory, C:\Program Files (x86)\Scribe Software\TIBCO Scribe® Online Agent\logs\.

          Note: For information on setting log file verbosity, see Verbosity in the CData Help.

        • MaxLogFileCount — This parameter is set by the Connector to a maximum of five files.
        • MaxLogFileSize — This parameter is set by the Connector to a maximum of 10MB.
        • Other
        • RTK
        • UseConnectionPooling
  4. Select Test to ensure that the Agent can connect to your database. Be sure to test the Connection against all Agents that use this Connection. See Testing Connections.
  5. Select OK to save the Connection.

Metadata Notes


Connection metadata must have unique entity, relationship, and field names. If your Connection metadata has duplicate names, review the source system to determine if the duplicates can be renamed.


PostgreSQL Entity names shown in TIBCO Scribe® Online display both the schema name and the entity name in the following format:




All arrays are considered strings, regardless of the data type of the values within the array.

When mapping or filtering on array fields, the value of the array must be enclosed in curly braces ({}), the values must be separated by commas, and the entire array must be enclosed in quotes because arrays are considered strings for the PostgreSQL Connector.


"{Text4, Text5, Text6}"
"{1, 100, 1000}"

Data Types

PostgreSQL data types are converted as follows: 

PostgreSQL Data Type

TIBCO Scribe® Online Data Type







(Not supported)



double precision






(Not supported)











(Not Supported)



All other types


All character, enumerated, geometric, network address, bit string, text search, UUID, XML, JSON, array, composite, range types are exposed as strings

PostgreSQL Connector As IS Source

Consider the following when using the PostgreSQL Connector as an Integration Solution source.


Net Change

Using Net Change to query for new and updated records is supported for date and timestamp fields. For Filters all logical and comparison operators are supported.

When a datetime is configured on the Query Block on the Block Properties Net Change Tab to query for new and updated records, that configuration is treated as an additional filter. The Net Change datetime filter is applied as an AND after any other filters specified on the Block Properties Filter Tab. TIBCO Scribe® Online builds a query combining both the Net Change filter and the filters on the Filter tab. See Net Change And Filters for an example.

Some Connectors for TIBCO Scribe® Online only support one filter. For those Connectors you can use either Net Change or one filter on the Filter tab, not both.

Note: The Net Change date is ignored when previewing data on the Preview tab. Filters on the Block Properties Filters tab are used to filter the data on the Preview tab.

Note: PostgreSQL fields that are data type Date do not have a time associated with them and therefore are not the best option for Net Change.  Best practice when configuring Net Change is to use a field that is data type Timestamp and includes timezone.

Native Query

The PostgreSQL Connector supports SQL queries in Native Query Blocks to create customized queries for PostgreSQL. The query can be as simple or complex as you need it to be; however, it should return a single result set. The native query text is sent to PostgreSQL exactly as it is entered without any modifications.

Note: It is possible to perform a SQL query with unintended negative consequences, such as dropping a table. TIBCO recommends that you use only SELECT clauses in the Native Query Block.

After entering the SQL query, you must select Test to validate the query. Invalid queries are not accepted by the Connector. See Native Query Block and Creating Native Queries For Microsoft SQL Server for additional information.

When using SQL queries, you must reference both the schema name and the table name, as shown in the following examples:

Select * from schemaname.tablename

Select * from bfschema1.table1

Note: If the schema is not referenced in the query, the default schema configured in the PostgreSQL database is used.

When testing a Native Query in a Map, if the source datastore does not return any data, TIBCO Scribe® Online cannot build the schema for the underlying metadata and the Map cannot be saved. To allow TIBCO Scribe® Online to build the schema, do the following:

  1. Create a single temporary record in the source datastore that matches the Native Query.
  2. Test the Native Query and ensure that it is successful.
  3. Save the Map.
  4. Remove the temporary record from the source datastore.

PostgreSQL Connector As IS Target

Consider the following when using the PostgreSQL Connector as an IS target.

TIBCO Scribe® Online API Considerations

To create connections with the TIBCO Scribe® Online API, the PostgreSQL Connector requires the following information:

Connector Name


Connector ID


TIBCO Scribe® Online Connection Properties

In addition, this Connector uses the Connection properties shown in the following table.

Note: Connection property names are case-sensitive.

Name Data Type Required Secured Usage































License Agreement

The TIBCO Scribe® Online End User License Agreement for the PostgreSQL Connector describes TIBCO and your legal obligations and requirements. TIBCO suggests that you read the End User License Agreement.

More Information

For additional information on this Connector, refer to the Knowledge Base and Discussions in the TIBCO Community.