Create replication slot in pg_basebackup if requested

When you create a replication slot, PostgreSQL keeps track of the changes that need to be sent to that slot start_replication(slot_name=

The timeline ID associated with restart_lsn , following the current timeline history START_REPLICATION XXXXXX [ TIMELINE

start replication slot postgres You can verify this by setting the slotName extra connection attribute to the name of this logical replication slot For more information, see Extra

slot canyon flash flood What are the long-running processes running START_REPLICATION queries on my Heroku Postgres database? Issue You are inspecting the pg_stat_activity view on