The downside of this waiting is that it means that GRANT and REVOKE will take longer than the longest currently executing transaction. This means that by the time the transaction which performed the grant or revoke operation returns successfully, the user has a proof that no ongoing transaction is relying on the state that existed prior to the change. By default, when granting or revoking a role from another role, CockroachDB waits for all transactions that are consulting the current set of role memberships to complete. Added a new session variable allow_role_memberships_to_change_during_transaction which can be used to make the granting and revoking of role memberships faster at the cost of some isolation claims.This setting can be used to ensure client cert expirations are exported as a metric (if set to zero, the metric will have a value of zero). There is a new server.client_cert_expiration_cache.capacity cluster setting which, when set to a non-zero number, makes it so that the minimum time-until-expiration of the set of client certificates seen is stored (for every user).View a detailed changelog on GitHub: v22.2.10.v22.2.11 Security updates $ docker pull cockroachdb/cockroach:v22.2.11
0 kommentar(er)
