Ran into a bug while migrating to major versioned replication slots.
Pattern for config file/server name is db1-table for old and db1-table-v17 for new.
Trying to decommission the old one with barman receive-wal --stop or barman list-process for db1-table is actually hitting the process of db1-table-v17 or in the case of list-process listing both processes
Greedy matching on lock files are never checked if they match server name from config looks to be the issue to my untrained eyes on this codebase
Running on 3.18.0
Ran into a bug while migrating to major versioned replication slots.
Pattern for config file/server name is
db1-tablefor old anddb1-table-v17for new.Trying to decommission the old one with
barman receive-wal --stoporbarman list-processfordb1-tableis actually hitting the process ofdb1-table-v17or in the case of list-process listing both processesGreedy matching on lock files are never checked if they match server name from config looks to be the issue to my untrained eyes on this codebase
Running on 3.18.0