If we have systems where we've created blueprints that included a bp_oximeter_read_policy row and then subsequently deleted that blueprint, we would have leaked that row because of #8436. If we've never done this on production systems, there may be nothing to do here. But if we have, then I imagine we want to do something like:

SELECT * FROM bp_oximeter_read_policy WHERE blueprint_id NOT IN (SELECT blueprint_id FROM blueprint);
DELETE FROM bp_oximeter_read_policy WHERE blueprint_id NOT IN (SELECT blueprint_id FROM blueprint);

We could maybe do this as a schema update, or else we could tack it onto the R16 update procedure?

@karencfv could you get to ground on this?