Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Have last cache configuration changes go through WAL #25172

Open
Tracked by #25091
hiltontj opened this issue Jul 19, 2024 · 1 comment
Open
Tracked by #25091

Have last cache configuration changes go through WAL #25172

hiltontj opened this issue Jul 19, 2024 · 1 comment
Labels

Comments

@hiltontj
Copy link
Contributor

hiltontj commented Jul 19, 2024

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.

@pauldix
Copy link
Member

pauldix commented Jul 19, 2024

Good to hold off on this until #25144 lands

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants