Use `server.dirty++` instead if `forceCommandPropagation` on FUNCTION commands (#9945)
Functions are considered data, so changing a function should be counted as a data change and should affect the persistence policy. For example if we want to persist an RDB each minute if there was a single change, functions should be counted as such change. Using `forceCommandPropagation` will not give us the desired effect and so we must switch to `server.dirty++`
Please register or sign in to comment