Babelfish for Aurora PostgreSQL updates - Amazon Aurora
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China.

Babelfish for Aurora PostgreSQL updates

Following, you can find information about versions of the Babelfish that have been released for Aurora PostgreSQL. Babelfish is an option available with Aurora PostgreSQL version 13.4 and higher releases. Updates to Babelfish become available with certain new releases of the Aurora PostgreSQL database engine.

For information about Aurora PostgreSQL extensions with Babelfish, see Using Aurora PostgreSQL extensions with Babelfish.

For information about Babelfish version updates, see Babelfish version updates.

For a list of supported and unsupported functionality across different Babelfish releases, see Babelfish for Aurora PostgreSQL reference.

Babelfish for Aurora PostgreSQL 2.2

This release of Aurora Babelfish is provided with Aurora PostgreSQL 14.5. For more information about the improvements in Aurora PostgreSQL 14.5, see Amazon Aurora PostgreSQL updates. Babelfish for Aurora PostgreSQL 2.2 adds several new features, enhancements, and fixes. For more information about Babelfish for Aurora PostgreSQL, see Working with Babelfish for Aurora PostgreSQL.

Aurora Babelfish release 2.2.0, November 9, 2022

Security enhancements

High priority stability enhancements

  • Fixed error handling in sp_prepare calls which can cause a server crash when a large number of parameters are sent by the application. Babelfish currently supports a maximum of 100 parameters for a procedure or function.

  • Fixed error handling in SSL/TLS handshake for some client drivers.

  • Fixed an issue where a login can access the database without creating DB user after the DROP/CREATE of login.

  • Fixed an issue where a login isn't dropped if it is logged in on any session.

New features

  • Support for data migration using the BCP client and the bcp utility now supports -E flag (for identity columns) and -b flag (for batching inserts).

  • Support for cross-database stored procedure execution.

  • Support for CROSS APPLY and OUTER APPLY (lateral join).

  • Support for built-in functions SYSTEM_USER, HOST_NAME; the Hostname is visible in the sys.sysprocesses T-SQL view; the SID_BINARY function is supported but always returns NULL in Babelfish.

  • Support for CAST function of numeric expressions to DATETIME.

  • Support for @@LANGUAGE variable with constant value as 'us_english’.

  • Support for the old-style function calls with '::' preceding the function name.

  • Support for the sp_helpsrvrolemember stored procedure.

  • Support for the msdb.dbo.fn_syspolicy_is_automation_enabled system function.

  • Support for more catalogs: assembly_types, numbered_procedures, triggers, spatial_index_tessellations, plan_guides, synonyms, events, trigger_events, fulltext_indexes, dm_hadr_cluster, xml_indexes, change_tracking_tables, key_constraints, database_filestream_options, filetable_system_defined_objects, hash_indexes, filegroups, master_files, assembly_modules, change_tracking_databases, database_recovery_status, fulltext_catalogs, fulltext_stoplists, fulltext_indexes, fulltext_index_columns, fulltext_languages, selective_xml_index_paths, spatial_indexes, filetables, registered_search_property_lists, syspolicy_configuration, syspolicy_system_health_state.

  • Support for new INFORMATION_SCHEMA catalogs: COLUMN_DOMAIN_USAGE, CONSTRAINT_COLUMN_USAGE, CHECK_CONSTRAINTS, ROUTINES, VIEWS.

  • Support for new PG-style query plan: escape hatch 'babelfish_pgtsql.escape_hatch_showplan_all'.

    • when set to 'ignore', SET SHOWPLAN_ALL and SET STATISTICS PROFILE behaves as SET BABELFISH_SHOWPLAN_ALL and SET BABELFISH_STATISTICS PROFILE.

    • when set to 'strict', SET SHOWPLAN_ALL and SET STATISTICS PROFILE are silently ignored.

  • Support for executing stored procedures with the sp_ prefix in the master database without using a three-part name.

Additional improvements and enhancements

  • Fixed an issue where a value of 1900-01-01 00:00:00 was stored when a NULL was inserted or updated into a datetime column. A NULL value is inserted now. Column values in tables created in a previous Babelfish release are not affected.

  • TIME datatypes that return 7 digits in SQL Server now returns 7 digits in Babelfish as well, with the 7th digit always being zero. In addition, a rounding issue that sometimes affected the 6th digit has been resolved.

  • Increased parameter lengths for @tsql and @params for sp_describe_first_result_set from nvarchar(384) to nvarchar(8000). This increases the number of columns the DMS Babelfish target endpoint can support from 25 to 1000.

  • Improved performance for system stored procedures: sys.sp_tablecollations_100, sp_columns_managed, and sp_describe_undeclared_parameters. This fix improves the performance of the DMS Babelfish target endpoint, SQL Server Management Studio import and export wizard, and prevents timeouts.

  • Fixed an issue with Bitwise NOT ~ operator and it returns the correct result with BIT data types now.

  • Fixed an issue with BCP when it is used for tables that have triggers.

  • Fixed an issue of backend failure in INSERT BULK when using Import-Export wizard.

  • Fixed an issue where SQL Server Management Studio (SSMS) returns an error while expanding "Triggers" for a table in the Object Explorer view.

  • Fixed an issue where the name column in the sys.sysobjects view was using case sensitive collation.

  • Fixed an issue to refer SQL objects inside a function and is resolved to the function's schema rather than the default schema of the user.

  • Fixed an issue where a backend crash can occur when using the ISNULL function with CONVERT on computed columns.

  • Fixed an issue with the DATEPART function when the date argument is a string literal.

  • Fixed an issue where a role can be dropped even if it has members.

  • Fixed an issue so that the db user can't add to a role or drop from a role.

  • Fixed an issue to allow BCP to work correctly with collations other than English collations.

  • Fixed an issue to make sp_helpuser procedure show login name for dbo user.

  • Fixed an issue to handle NULL and mix-cased inputs correctly for the functions SUSER_SNAME and SUSER_SID.

  • Fixed an issue with Babelfish returning an invalid TDS protocol stream when there is a numeric overflow error.

  • Fixed an issue where is_fixed_role column returns incorrect value in the sys.server_principals view for the 'sysadmin' role.

  • Fixed the transaction error handling in a batch if the string passed to execute contains a USE dbname and fails because the database dbname was not found.

  • Fixed the issue with procedures created in master database context with prefix sp_ that are not accessible from other database context.

  • Fixed the failure to resolve object name inside a procedure when used with schema name.

  • Fixed case-sensitivity issue with arguments to the functions USER_ID and SUSER_ID.

  • Fixed an issue where triggers were allowed to be created on Babelfish temporary tables.

  • Fixed several performance issues with Import-Export wizard.

  • Support for multi-byte client encodings other than UTF-16 for VARCHAR(n).

  • Fixed the system compatibility view sys.sysprocesses to show the correct value for hostname provided by the client connection.

  • Fixed case sensitivity issue with Polish_CI_AS collation.

  • Fixed the @@DBTS function so that value of @@DBTS correctly returns the current transaction id after each DML statement even when used within a transaction.

  • Improved performance for queries that refer to the functions SCOPE_IDENTITY and @@IDENTITY.

  • Support added for collations Japanese_CS_AS, Japanese_CI_AI and Japanese_CI_AS for fn_helpcollations.

  • @@SERVERNAME and SERVERPROPERTY('ServerName') now return the name of the Babelfish instance as specified by the user when the instance is created. This value is also returned by the newly supported properties SERVERPROPERTY('MachineName') and SERVERPROPERTY('InstanceName').

  • Function fn_mapped_system_error_list lists the PG error code mapped to @@ERROR codes, as well as the corresponding error message text. This function also exists in previous Babelfish releases but did not include mapping details.

  • Fixed DATEADD function to now support milliseconds(ms) time units.

  • SET NO_BROWSETABLE {ON|OFF} is now subject to escape hatch escape_hatch_session_settings, so no error is raised when set to ignored.

  • SET PARSEONLY {ON|OFF} is now supported. Previously this would raise an error unless escape hatch escape_hatch_session_settings is set to ignored.

  • The DATABASE_DEFAULT AND CATALOG_DEFAULT collation is now supported; this refers to the server/instance-level collation that was specified when the Babelfish instance was created, as Babelfish doesn't currently support collations on database level.

  • For the functions OBJECTPROPERTY and OBJECTPROPERTYEX, the following properties are now supported: ExecIsAnsiNullsOn, ExecIsQuotedIdentOn, IsDefault, IsDefaultCnst, IsDeterministic, IsIndexed, IsInlineFunction, IsMSShipped, IsPrimaryKey, IsProcedure, IsRule, IsScalarFunction, IsSchemaBound, IsTable, IsTableFunction, IsTrigger, IsUserTable, IsView, OwnerId, TableFulltextPopulateStatus, TableHasVarDecimalStorageFormat.

  • OBJECTPROPERTYEX function supports the BaseType property.

  • INDEXPROPERTY function supports the following properties: IndexFillFactor, IndexID, IsClustered, IsDisabled, IsHypothetical, IsPadIndex, IsPageLockDisallowed, IsRowLockDisallowed, IsUnique.

Babelfish for Aurora PostgreSQL 2.1

This release of Aurora Babelfish is provided with Aurora PostgreSQL 14.3 and 14.4. For more information about the improvements in Aurora PostgreSQL 14.3 and 14.4, see Amazon Aurora PostgreSQL updates. Babelfish for Aurora PostgreSQL 2.1 adds several new features, enhancements, and fixes. For more information about Babelfish for Aurora PostgreSQL, see Working with Babelfish for Aurora PostgreSQL.

Babelfish for Aurora PostgreSQL release 2.1.2, October 18, 2022

Security enhancements

High priority stability enhancements

  • Fixed error handling in sp_prepare calls which can cause a server crash when a large number of parameters are sent by the application. Babelfish currently supports a maximum of 100 parameters for a procedure or function.

  • Fixed error handling in SSL/TLS handshake for some client drivers.

Babelfish for Aurora PostgreSQL release 2.1.1, July 6, 2022

  • Fixed the babelfishpg_tds extension to correctly allocate the shared memory size used by the extension.

Babelfish for Aurora PostgreSQL release 2.1.0, June 21, 2022

Babelfish DB clusters running on Aurora PostgreSQL 13.7 or older versions can't be upgraded to Aurora PostgreSQL 14.3 with Babelfish 2.1.0.

New features

  • Support for data migration using the bcp client utility, as an experimental feature. Some bcp options (-b, -C, -E, -G, -h, -K, -k, -q, -R, -T, -V) are not currently supported.

  • Support for connecting with the SSMS object explorer connection dialog (rather than only the Query Editor connection dialog), as well as partial support for the SSMS object explorer itself.

  • Improved support for data migration with the SSMS Import/Export Wizard.

  • Support for IS_MEMBER, IS_ROLEMEMBER, and HAS_PERMS_BY_NAME functions.

  • Support for syslanguages, sys.indexes, sys.all_views, sys.database_files, sys.sql_modules, sys.system_sql_modules, sys.all_sql_modules, sys.xml_schema_collections, sys.dm_hadr_database_replica_states, sys.data_spaces, sys.database_mirroring, sys.database_role_members catalogs.

  • Support for sp_sproc_columns, sp_sproc_columns_100, sp_helprole, sp_helprolemember system stored procedures.

  • Support for Japanese_CS_AS, Japanese_CI_AI, Japanese_CI_AS collations.

  • Babelfish now supports CHARINDEX substring searches on systems using nondeterministic collations.

  • Babelfish now supports PATINDEX, and supports arguments to STRING_SPLIT that are collated using a case-insensitive collation.

  • Query plan output is generated following SET BABELFISH_SHOWPLAN_ALL ON (and OFF) and SET BABELFISH_STATISTICS PROFILE ON (OFF). This will generate PostgreSQL-style query plan information for T-SQL queries in Babelfish. Make sure these SET statements are identical to existing T-SQL statements, but with the added BABELFISH_ prefix.

Additional improvements and enhancements

  • Cross–database references outside the current database, with a 3-part object name, for SELECT,SELECT..INTO, INSERT, UPDATE, DELETE.

  • CREATE ROLE (AUTHORIZATION clause not supported), DROP ROLE, ALTER ROLE.

  • Babelfish now maps the error code for @@ERROR=213. For more information on error handling, see Managing Babelfish error handling.

  • Fixed an issue with SUBSTRING(CHARINDEX()) variable assignment that caused Babelfish to become unavailable.

  • Fixed an issue with INSERT INTO...with OUTPUT clause that resulted in a Number of given values doesn't match target table definition error.

  • Fixed an issue that caused DELETE with OUTPUT INTO temporary table statements to return a WITH query 'nnnnnnnnnnn' doesn't have a RETURNING clause error.

  • Fixed an issue that caused LEFT OUTER JOIN to fail with a Sqlcmd: Error: Internal error at ReadAndHandleColumnData (Reason: Error reading column data) error. This issue was a regression introduced in Babelfish 1.1.0. If your Babelfish for Aurora PostgreSQL DB cluster runs Babelfish version 1.1.0 and you get this error, we recommend that you upgrade to Aurora PostgreSQL 13.7 to obtain this fix.

  • Fixed an invalid syntax error using the GETUTCDATE() and SYSUTCDATETIME() built-in functions.

  • Fixed an issue where numeric overflow conditions using SUM() and AVG() functions caused a TDS error.

  • Fixed an issue with .NET applications calling store procedures for a DataTable object that resulted in a datatype mismatch and disallowed implicit casting error.

Babelfish for Aurora PostgreSQL 1.4

This release of Aurora Babelfish is provided with Aurora PostgreSQL 13.8. For more information about the improvements in Aurora PostgreSQL 13.8, see Amazon Aurora PostgreSQL updates. The following issues are resolved in Babelfish for Aurora PostgreSQL 1.4 release. For more information about Babelfish for Aurora PostgreSQL, see Working with Babelfish for Aurora PostgreSQL.

Aurora Babelfish release 1.4.0, November 9, 2022

Security enhancements

High priority stability enhancements

  • Fixed error handling in sp_prepare calls which can cause a server crash when a large number of parameters are sent by the application. Babelfish currently supports a maximum of 100 parameters for a procedure or function.

  • Fixed error handling in SSL/TLS handshake for some client drivers.

Additional improvements

  • Fixed the babelfishpg_tds extension to correctly allocate the shared memory size used by the extension.

Babelfish for Aurora PostgreSQL 1.3

This release of Aurora Babelfish is provided with Aurora PostgreSQL 13.7. For more information about the improvements in Aurora PostgreSQL 13.7, see Amazon Aurora PostgreSQL updates. The following issues are resolved in Babelfish for Aurora PostgreSQL 1.3 release. For more information about Babelfish for Aurora PostgreSQL, see Working with Babelfish for Aurora PostgreSQL.

Babelfish for Aurora PostgreSQL release 1.3.2, October 18, 2022

Security enhancements

High priority stability enhancements

  • Fixed error handling in sp_prepare calls which can cause a server crash when a large number of parameters are sent by the application. Babelfish currently supports a maximum of 100 parameters for a procedure or function.

  • Fixed error handling in SSL/TLS handshake for some client drivers.

Babelfish for Aurora PostgreSQL release 1.3.1, July 6, 2022

  • Fixed the babelfishpg_tds extension to correctly allocate the shared memory size used by the extension.

Babelfish for Aurora PostgreSQL release 1.3.0, June 9, 2022

  • Fixed an issue with SUBSTRING(CHARINDEX()) variable assignment that caused Babelfish to become unavailable.

  • Fixed an issue with INSERT INTO...with OUTPUT clause that resulted in a Number of given values doesn't match target table definition error.

  • Fixed an issue that caused DELETE with OUTPUT INTO temporary table statements to return a WITH query 'nnnnnnnnnnn' doesn't have a RETURNING clause error.

  • Fixed an issue that caused LEFT OUTER JOIN to fail with a Sqlcmd: Error: Internal error at ReadAndHandleColumnData (Reason: Error reading column data) error. This issue was a regression introduced in Babelfish 1.1.0. If your Babelfish for Aurora PostgreSQL DB cluster runs Babelfish version 1.1.0 and you get this error, we recommend that you upgrade to Aurora PostgreSQL 13.7 to obtain this fix.

Babelfish for Aurora PostgreSQL 1.2

This release of Babelfish is provided with Aurora PostgreSQL 13.6. For more information about the improvements in Aurora PostgreSQL 13.6, see Amazon Aurora PostgreSQL updates. The following issues are resolved in Babelfish 1.2 release. For more information about Babelfish, see Working with Babelfish for Aurora PostgreSQL.

Babelfish for Aurora PostgreSQL release 1.2.3, October 18, 2022

Security enhancements

Babelfish for Aurora PostgreSQL release 1.2.2, July 18, 2022

  • Fixed an issue causing outer join queries to sometimes fail with an internal error message.

  • Fixed the babelfishpg_tds extension to correctly allocate the shared memory size used by the extension.

Babelfish for Aurora PostgreSQL release 1.2.1, April 27, 2022

  • Fixed an issue that caused Babelfish to become unavailable after working with temporary tables.

  • Fixed an issue that prevented successful minor version upgrade from a Babelfish for Aurora PostgreSQL 13.4 or 13.5 DB cluster to Aurora PostgreSQL 13.6.

  • Fixed an issue that prevented transferring data to a table with identity columns using the SQL Server Management Studio import and export wizard.

Babelfish for Aurora PostgreSQL release 1.2.0, March 29, 2022

In addition to the new features and improvements in the following list, Babelfish for Aurora PostgreSQL 1.2.0 adds several features that currently have limited implementations. These features are available for use but don't yet have complete parity with T-SQL syntax or Microsoft SQL Server. For more information, see Features with limited implementation.

  • Casing (upper-case, lower-case) of column names as created with T-SQL is now retained. That is, SELECT * FROM table returns the column names using the same casing as used when the table was created at the TDS endpoint.

  • INSTEAD-OF triggers are now supported on tables (tables only, not views).

  • Support for system-defined global variables @@DBTS, @@LOCK_TIMEOUT, @@SERVICENAME.

  • Support for syntax SET LOCK_TIMEOUT.

  • Support for datatypes TIMESTAMP and ROWVERSION.

  • Support for built-in functions COLUMNS_UPDATED, UPDATE, FULLTEXTSERVICEPROPERTY, ISJSON, JSON_QUERY, JSON_VALUE, HAS_DBACCESS, SUSER_SID, SUSER_SNAME, IS_SRVROLEMEMBER.

  • Full support for the CHECKSUM function. This function now supports * and multiple columns (CHECKSUM ( * | expression [ ,...n ] )).

  • Full support for the SCHEMA_ID function. This function can now be used without any arguments (SCHEMA_ID ( [ schema_name ] )).

  • Support for DROP IF EXISTS with SCHEMA, DATABASE, and USER objects.

  • Support for these additional values for CONNECTIONPROPERTY: physical_net_transport and client_net_address.

  • Support for the these SERVERPROPERTY values: EditionID, EngineEdition, LicenseType, ProductVersion, ProductMajorVersion, ProductMinorVersion, IsIntegratedSecurityOnly, IsLocalDB, IsAdvancedAnalyticsInstalled, IsBigDataCluster, IsPolyBaseInstalled, IsFullTextInstalled, and IsXTPSupported.

  • Support for these catalogs: sys.dm_os_host_info, sys.dm_exec_sessions, sys.dm_exec_connections, sys.endpoints, sys.table_types, sys.database_principals, sys.sysprocesses, sys.sysconfigures, sys.syscurconfigs, and sys.configurations.

  • Support for these INFORMATION_SCHEMA catalogs: TABLES, COLUMNS, DOMAINS, and TABLE_CONSTRAINTS.

  • Support for these system stored procedures: sp_table_privileges, sp_column_privileges, sp_special_columns, sp_fkeys, sp_pkeys, sp_stored_procedures, xp_qv, sp_describe_undeclared_parameters, and sp_helpuser.

  • Limited support for creating, altering, and dropping database principals (USER objects). Limitations for CREATE/ALTER/DROP syntax with USER objects are as follows:

    • For CREATE USER, you can specify the FOR/FROM LOGIN and DEFAULT_SCHEMA options only.

    • For ALTER USER, you can specify DEFAULT_SCHEMA option only.

  • Limited support for the SET FMTONLY ON command. Setting this command ON suppresses the execution of SELECT statements only. It doesn't suppress the execution of other statements.

  • Support for granting and revoking (GRANT/REVOKE) permisions for database principals only (not database roles). Support includes GRANT OPTION and REVOKE..CASCADE options for SELECT, INSERT, UPDATE, DELETE, REFERENCES, EXECUTE, and ALL [PRIVILEGES].

  • Support for WITH AUTHORIZATION on CREATE SCHEMA.

  • Support for the following new escape hatches and escape hatch functionality:

    • Restore all default settings for escape hatches for your Babelfish DB instance by passing default as the second argument to the sp_babelfish_configure stored procedure.

    • A new escape hatch, escape_hatch_ignore_dup_key (default=strict) controls the IGNORE_DUP_KEY option in CREATE/ALTER TABLE and CREATE INDEX statements. When IGNORE_DUP_KEY=ON, an error is raised unless escape_hatch_ignore_dup_key is set to 'ignore'.

    • Added support for the ignore option on the escape_hatch_storage_options escape hatch. When set to ignore, Babelfish ignores errors raised in the following cases:

      • Ignores errors raised in the ON clause in a CREATE DATABASE statement.

      • Ignores errors raised by CREATE INDEX when used with SORT_IN_TEMPDB, DROP_EXISTING, or ONLINE options.

    For details, see Managing Babelfish error handling.

  • The msdb system database is always present, and has dbid=4. For more information, see Babelfish architecture.

  • For a list of features supported in each Babelfish release, see Supported functionality in Babelfish by version.

Babelfish for Aurora PostgreSQL 1.1

This release of Babelfish is provided with Aurora PostgreSQL 13.5. For more information about the improvements in Aurora PostgreSQL 13.5, see Amazon Aurora PostgreSQL updates. The following issues are resolved in Babelfish 1.1 release. For more information about Babelfish, see Working with Babelfish for Aurora PostgreSQL.

Babelfish for Aurora PostgreSQL release 1.1.1, October 18, 2022

Security enhancements

Babelfish for Aurora PostgreSQL release 1.1.0, February 25, 2022

Babelfish for Aurora PostgreSQL version 1.1.0 adds support for the following Microsoft SQL Server functionality and T-SQL commands. For more information, see Working with Babelfish for Aurora PostgreSQL.

  • Unique indexes or UNIQUE constraints on nullable columns. To use this capability, change the escape_hatch_unique_constraint to 'ignore'. For more information, see Managing Babelfish error handling

  • Reference transition tables from triggers with multiple DML actions.

  • Identifiers that have leading dot characters.

  • The COLUMNPROPERTY function (limited to CharMaxLen and AllowsNull properties).

  • System-defined @@ variables: @@CURSOR_ROWS, @@LOCK_TIMEOUT, @@MAX_CONNECTIONS, @@MICROSOFTVERSION, @@NESTLEVEL, and @@PROCID.

  • Built-in functions: CHOOSE, CONCAT_WS, CURSOR_STATUS, DATEFROMPARTS, DATETIMEFROMPARTS, ORIGINAL_LOGIN, SCHEMA_NAME (now fully supported), SESSION_USER, SQUARE, and TRIGGER_NESTLEVEL supported (but only without arguments).

  • System stored procedures: sp_columns, sp_columns_100, sp_columns_managed, sp_cursor, sp_cursor_list, sp_cursorclose, sp_cursorexecute, sp_cursorfetch, sp_cursoropen, sp_cursoroption, sp_cursorprepare, sp_cursorprepexec, sp_cursorunprepare, sp_databases, sp_datatype_info, sp_datatype_info_100, sp_describe_cursor, sp_describe_first_result_set, sp_describe_undeclared_parameters, sp_oledb_ro_usrname, sp_pkeys, sp_prepare, sp_statistics, sp_statistics_100, sp_tablecollations_100, sp_tables, and sp_unprepare.

  • For a list of features supported in each Babelfish release, see Supported functionality in Babelfish by version.

Babelfish for Aurora PostgreSQL 1.0

This release of Babelfish is provided with Aurora PostgreSQL 13.4. For more information about the improvements in Aurora PostgreSQL 13.5, see Amazon Aurora PostgreSQL updates. The following issues are resolved in Babelfish 1.0 release. For more information about Babelfish, see Working with Babelfish for Aurora PostgreSQL.

Babelfish for Aurora PostgreSQL release 1.0.1, October 18, 2022

Security enhancements

Babelfish for Aurora PostgreSQL release 1.0.0, October 28, 2021

  • Babelfish for Aurora PostgreSQL version 1.0.0 supports Babelfish 1.0.0 which extends your Amazon Aurora PostgreSQL database with the ability to accept database connections from Microsoft SQL Server clients. For more information, see see Working with Babelfish for Aurora PostgreSQL.