YugabyteDB agent changelog

YugabyteDB: documented the source prerequisites that apply to YugabyteDB rather than the PostgreSQL ones, including that wal2json ships with the server and that the limits to raise are the YB-Master max_replication_slots flag and max_wal_senders;

GSSD-1120: Fixed deduplication logic for primary keys columns with case insensitive collation;

Fixed issue where the message read loop could break while a transaction is in progress;

Added possibility to change wal sender timeout value;

Improved error handling when no replication slot is available;

GSSD-1118: Fixed transaction loss when connection lost;

GSSD-1092: Insert query improvements;

Added support for PgVector data type;

Fixed write connection not closed in some circumstances;

Fixed insert query without physical primary key causing failure of "on conflict" statement in query;

Added precision fallback for null datetime precision;

Fixed primary key matching with NULL values in SQL queries;

Removed primary keys constraint from temp tables;

Improved support for enhaced columns discovery (precision, lenght, scale);

Snapshot performance enhancements;

Fixed an issue that was causing the agent to display a wrong e2e timing;

Improved performance and stability;

GSSD-721: Fixed an issue that was causing the agent to fail with "Binary Write Failed" error (org.postgresql.util.PSQLException: ERROR: value too long for type character(1));

GSSD-749: Fixed an incompatibility issue with the PostGIS extension;

GSSD-654: Improved error handling and resilience when dealing with high latency connections;

Optimized metadata queries;

Replace drop of staging table with Truncate operation in case of Bulk loads usage;

Agent compatibility upgrade to Gluesync 2.2;