Version 2.4.4 is a maintenance release of pglogical 2.

Changes

• Add support for PostgreSQL 16.

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.

Version 2.4.2 is a maintenance release of pglogical 2.

Changes

• Add support for PostgreSQL 15.

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

Version 2.4.0 is a maintenance release of pglogical 2.

Changes

• Add preliminary support for PostgreSQL 14 (beta)

• Fix pglogical_show_subscription_table to 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_subscriber on Windows

• Fix double closing of relation when a BEFORE ROW DELETE trigger 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_string is always set
  Newer versions of PostgreSQL require that debug_query_string is always set.

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_ctl with appropriate verbosity in pglogical_create_subscriber

  When -v is passed to pglogical_create_subscriber, it will now call pg_ctl without silent mode. This is useful for troubleshooting.

• Clarify documentation regarding REPLICA IDENTITY requirements and support

This release adds support for PostgreSQL 13.

pglogical 2.3.2 fixes the build against the latest PostgreSQL minor releases (9.5.22, 9.6.18, 10.13, 11.8, 12.3). Existing binaries of older pglogical releases will continue to work with these new PostgreSQL releases, but compiling from source will require pglogical 2.3.2.

pglogical 2.3.1 contains several fixes that prevented users from upgrading to version 2.3.0.

The features "Allow replicating tables and sequences to different names on the target" and "Add option to only synchronize the structure of replicated relations" from pglogical 2.3.0 have been removed in this release for the time being and will be added again in a later release.

The pglogical 2.3.0 is a minor update to the pglogical 2 which includes support for PostgreSQL 12 and several new minor features and bug fixes.

Improvements

• Support for PostgreSQL 12
• Allow replicating tables and sequences to different names on the target
• Add option to only synchronize the structure of replicated relations
• Add a new option to force a text transfer format for a subscription
• Allow tables to be resynchronized in state SYNC_STATUS_SYNCDONE
• Fix pglogical_wait_for_sync_complete with unknown table
• Use write lsn rather than insert lsn by default in wait_slot_confirm_lsn