Does something like this exist in postgres? The use case is an upgrade from postgres 10 to 11. The last time we upgraded (to 13), some queries turned out not t

Does something like this exist in postgres? The use case is an upgrade from postgres 10 to 11. The last time we upgraded (to 13), some queries turned out not to work well, so we were forced to go back to the old server. In the meantime stuff was written to the new server which we then manually put into the old db before switching over to the old. Result: lots of downtime. Is there a way to create a changeset like this in postgres?