I mean advisory locks are ultimately rows too. Managing a job ownership table isn’t gonna produce a whole lot more garbage than dead advisory lock rows. Both will produce some but ultimately we need to just trust VACUUM to do its job properly. It may also be possible to simply put the node information in the job row itself, I need to think through the details some.
EDIT: One option that would help with this specific issue is to just have a single dedicated process per node hold the locks. This probably isn’t performant enough however. I can get away with it in Fable because locks are only acquired on boot and then held for the whole time the node is up. The locks here are per job right?
)