PostgreSQL Release Notes
Release notes are displayed in descending order from the most recent release to the oldest. Known Issues are listed with the most recent release.
See TIBCO Scribe® Online Connector For PostgreSQL for more information.
Version 1.2.1
Released March 5, 2020.
New And Noteworthy
- Updated the ADO.NET data provider to version 0.11.2.0. (SCPOSTC-48)
- Updated the PostgreSQL CData Driver to version 19.0.7335.0.
Changes In Functionality
- CData logging is no longer enabled by default. To enable logging, set the Verbosity parameter to Verbosity=1 in the Additional Parameters field on the Connection dialog. Note that Verbosity can be set to any level 1 through 5 to enable logging, however, the higher the level the more information is logged. (SCPOSTC-136)
- MaxLogFileSize and MaxLogFileCount parameters are overridden by the Connector. MaxLogFileSize is set to 10MB and MaxLogFileCount is set to 5 files. When the maximum number of CData log files is reached, the oldest file is overwritten. (SCPOSTC-136)
Closed Issues
75256 / SCPOSTC-52
When PostgreSQL was deployed in an AWS RDS environment, the PostgreSQL Connector could not retrieve metadata. (Case # 01812880, 01730135, 01730415, 01730433, 01809216, 01790933)
Known Issues
SCPOST-162
Summary: Reusing existing connections to the PostgreSQL server that may have been closed by the server due to inactivity sometimes causes a fatal error to occur. (Case # 01891938, 01905520)
Workaround: None.
SCPOST-159
Summary: Mapping a datetime with no time zone offset to a PostgreSQL field that is type Timestamp with time zone, causes the time to be adjusted incorrectly.
Workaround: Verify that datetime information in the source contains a time zone offset.
SCPOST-158
Summary: Fields that are type Date are designated as type datetime in the Connector metadata, but have no time associated with them in PostgreSQL. When used as source data in TIBCO Cloud™ Integration - Connect, these fields are given a default time of midnight or 00:00:00 plus a UTC time zone offset based on the server time where the Connect on-premise agent is installed. For example if the date is 2020-12-31 and the agent is installed on a server in Boston, in TIBCO Cloud™ Integration - Connect it is converted to 2020-12-31T05:00:00Z.
Workaround: Use fields that are type timestamp.
SCPOSTC-148
Summary: Creating records in PostgreSQL fails when the table name contains a backslash (\) and one or more other special characters.
Workaround: Rename the table to remove the backslash character and reset metadata for the Connection.
Summary: In some cases, when using a Connect cloud agent with logging enabled, the first log file is created successfully but only a small amount of data is added.
Workaround: If you need logging to diagnose an issue, install a Connect on-premise agent and use that agent to run the app.
Version 1.1.1
Released January 3, 2019.
New And Noteworthy
- This release represents an alignment with TIBCO Scribe® branding and release processes.
- Added support for Insert, Update, and Delete operations for updatable views.
Closed Issues
67183 / 64222
PostgreSQL Connections intermittently failed with a timeout or a remote host closed the connection. (Case # 64719, 66638, 66627)
65706
PostgreSQL Connections that encountered record errors were not recovering and were unavailable for subsequent app executions. (Case # 64539)
Version 1.0.0
Released March 1, 2018.
New And Noteworthy
The Connector for PostgreSQL supports the following:
- Query, Native Query, Create, Update, and Delete operations for PostgreSQL databases.
- Net Change to query for new and updated records based on any date or timespan field.
- Entities based on the tables and views in the PostgreSQL database.
- All logical and comparison operators for Filters.
Closed Issues
There are no Closed Issues in this release.