> There is really no reasonable argument that master and slave is a good terminology to use for databases. That doesn't mean that it's reasonable to insist tha

> There is really no reasonable argument that master and slave is a good terminology to use for databases. That doesn't mean that it's reasonable to insist that all databases which already use this terminology should potentially break compatibility with prior versions of themselves simply because a handful of other people see the words "master" and "slave" and entirely ignore actual context in order to look "woke" (coming across as superficial and insincere in the process). It is what it is. Maybe there are more descriptive terms, but "master" and "slave" are descriptive enough.