Skip to content

Ensure to populate log_action cache when archiving using DB Reader, not using the Writer #20594

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

Merged
merged 1 commit into from
Apr 17, 2023

Conversation

tsteur
Copy link
Member

@tsteur tsteur commented Apr 16, 2023

For consistency with other archiving queries.

I know this feature is being removed in 5.x-dev but we're currently using for a few customers and it may increase the load on the writer quite a bit when it should use the reader for archiving related queries.

Review

…ot using the Writer

For consistency with other archiving queries.

I know this feature is being removed in 4.x-dev but we're currently using for a few customers and it may increase the load on the writer quite a bit when it should use the reader for archiving related queries.
@tsteur tsteur added the Needs Review PRs that need a code review label Apr 16, 2023
@tsteur tsteur added this to the 4.14.x milestone Apr 16, 2023
@sgiehl sgiehl merged commit 5086c43 into 4.x-dev Apr 17, 2023
@sgiehl sgiehl deleted the usereaderlogaction branch April 17, 2023 06:13
@sgiehl sgiehl modified the milestones: 4.14.x, 4.14.2 Apr 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs Review PRs that need a code review
Development

Successfully merging this pull request may close these issues.

2 participants