Releases: 2ndQuadrant/pglogical
pglogical 2.4.7
pglogical 2.4.6
Version 2.4.6 is a maintenance release of pglogical 2.
Changes
-
Add support for PostgreSQL 18.
-
Fix additional deadlock during DROP DATABASE.
-
Fix incorrect row_filter processing after cache invalidation.
pglogical 2.4.5
Version 2.4.5 is a maintenance release of pglogical 2.
Changes
- Add support for PostgreSQL 17.
- Fix index usage for conflict resolution.
- Maintain indexes when updating
pglogical.sequence_state. - Fix build on PostgreSQL 9.4.
pglogical 2.4.4
Version 2.4.4 is a maintenance release of pglogical 2.
Changes
- Add support for PostgreSQL 16.
pglogical 2.4.3
Version 2.4.3 is a maintenance release of pglogical 2.
Changes
- Apply data filtering on the correct tuple during initial synchronization.
- Restore the correct memory context while decoding a change.
- Drop database never completes in PostgreSQL 15.
- Don't replicate TRUNCATE as global message.
pglogical 2.4.2
Version 2.4.2 is a maintenance release of pglogical 2.
Changes
- Add support for PostgreSQL 15.
pglogical 2.4.1
Version 2.4.1 is a maintenance release of pglogical 2.
Changes
-
Fix "snapshot still active" warnings and snapshot handling with domains. Problems introduced in version 2.4.0.
-
Flush error state when having failed to drop remote replication slot
pglogical 2.4.0
Version 2.4.0 is a maintenance release of pglogical 2.
Changes
-
Add preliminary support for PostgreSQL 14 (beta)
-
Fix
pglogical_show_subscription_tableto return row rather than set of rows -
Fix snapshot handling in output plugin and apply worker
-
Fix command quoting on Windows so that it actually works
Seems like the API used before has 1024 limit on command line length -
Make sure that the schema syncing process can be interrupted on Windows
-
Fix compilation issues with
pglogical_create_subscriberon Windows -
Fix double closing of relation when a
BEFORE ROW DELETEtrigger returns NULL in the apply worker -
Fix multi-insert crash in the SPI apply worker
-
Fix multi-insert doing insert of last tuple multiple times in apply worker
-
Make sure
debug_query_stringis always set
Newer versions of PostgreSQL require thatdebug_query_stringis always set.
pglogical 2.3.4
Version 2.3.4 is security release fixing CVE-2021-3515.
Changes
-
Fix pg_dump/pg_restore execution (CVE-2021-3515)
Correctly escape the connection string for both pg_dump and pg_restore so that exotic database and user names are handled
correctly.Reported by Pedro Gallegos
-
Assign collation to the index scan key
When doing lookups for INSERT/UPDATE/DELETE, either to find conflicts or key for the operation to be applied, we should use correct collation.
This fixes issues with PostgreSQL 12+ primary key lookups when primary key is on column using one of the textual types.
-
Execute
pg_ctlwith appropriate verbosity inpglogical_create_subscriberWhen
-vis passed topglogical_create_subscriber, it will now callpg_ctlwithout silent mode. This is useful for troubleshooting. -
Clarify documentation regarding
REPLICA IDENTITYrequirements and support
pglogical 2.3.3
This release adds support for PostgreSQL 13.