text. It should be used in a way that makes conflicts between replication origins created by different replication solutions unlikely; e.g., by prefixing the replication solution's name to it. The OID is used only to avoid having to store the long version in situations where space efficiency is important. It should never be shared across systems.
pg_replication_origin_session_setup()function). Additionally the LSN and commit time stamp of every source transaction can be configured on a per transaction basis using
pg_replication_origin_xact_setup(). If that's done replication progress will persist in a crash safe manner. Replay progress for all replication origins can be seen in the
pg_replication_origin_statusview. An individual origin's progress, e.g., when resuming replication, can be acquired using
pg_replication_origin_progress()for any origin or
pg_replication_origin_session_progress()for the origin configured in the current session.
filter_by_origin_cbcallback can be used to filter the logical decoding change stream based on the source. While less flexible, filtering via that callback is considerably more efficient than doing it in the output plugin.