Safe deployment for database content

My application is deployed on several servers that all read data from a single database.

Following safe deployment practices, code deployments happen first on a subset of servers and only continue to the remaining servers if no issues are detected.

I’d like to also employ safe deployment practices for some critical data that is stored in the database. When appending new rows to a particular table, I’d like those rows to only be consumed by a subset of servers. The remaining servers will only consume the data if no issues are detected for a period of time.

How can I do this given that i only have a single database?