Skip to content

Babelfish 4.0.0 for PostgreSQL 16.1

Latest
Latest
Compare
Choose a tag to compare
@shardgupta shardgupta released this 09 Feb 12:45
BABEL_4_0_0__PG_16_1
a2ab3b3
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Overview

Babelfish 4.0.0 contains enhancements and fixes that improve the user experience, including:

New features

  • Added support for Full Text Search in Babelfish.
  • Added support for creating INSTEAD OF Triggers on Views.

Security enhancements

  • Fixed security issues with handling of TSQL login and users.

High Priority stability enhancements

  • Fixed a regression issue where update-join with inserted table in trigger procedure causes "result relation must be a regular relation" error
  • Fixed the issue where querying information_schema for type U and V was earlier giving difference result in Babelfish.
  • Fixed an issue to avoid blocking of vacuum progress when using temp tables in certain situations.

Additional improvements and enhancements

  • Fixed an issue with principal name in pg_stat_gssapi catalog view.
  • Fixed issue in functions parsename, session_context and sp_set_session_context when using with non-default server collation.

Upgrading to the new version

If you’re running Babelfish in a managed environment, please check your vendor’s instructions for upgrading.

MAJOR VERSION UPGRADE

Babelfish 4.0.0 provides the ability to upgrade from some 3.x.x versions of Babelfish. This process is called major version upgrade (MVU). It consists of two steps. First, you need to perform a major version upgrade on the PostgreSQL server to upgrade it to the target version. Second, you need to update all Babelfish extensions to the target version. Currently, Babelfish only supports upgrade using the pg_upgrade module. Other upgrade methods such as dump/restore and replication are not supported.

Assets 4