You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when last caches are created/deleted, there is no WAL entry for this configuration change, so these actions force persistence of the catalog before returning a success response to the caller, vs., creating a WAL entry and waiting for that to be flushed.
The purpose of this issue is to see if we can have these configuration changes, i.e., last cache create/delete be entered in the WAL.
The text was updated successfully, but these errors were encountered:
Currently, when last caches are created/deleted, there is no WAL entry for this configuration change, so these actions force persistence of the catalog before returning a success response to the caller, vs., creating a WAL entry and waiting for that to be flushed.
The purpose of this issue is to see if we can have these configuration changes, i.e., last cache create/delete be entered in the WAL.
The text was updated successfully, but these errors were encountered: