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

Release 2025.3.2 backmerge #1978

Merged
merged 7 commits into from
Jan 15, 2025
Merged

Release 2025.3.2 backmerge #1978

merged 7 commits into from
Jan 15, 2025

Conversation

kasperg
Copy link
Contributor

@kasperg kasperg commented Jan 15, 2025

No description provided.

The purge queues module uses an alternate database table name and
structure.

Due to problems with Azure MariaDB we are seeing tables missing and
but without being able to recreate them due to tablespaces exists.

Using Purge Queues allows us a clean solution to using a separate
table name and the potential of optimizing purge queue usage by
ensuring unique entries.
At this point we just want to use a separate database table. We are
OK with not using any of the optimizations.
We cannot wait for config import to do this as installing the module
will try to use the purge queue before config import is run.

Consequently we have to set the value manually in an update hook.

10032 has already been applied on staging with release 2025.3.1 so we
need to add a new update hook for this.
@kasperg kasperg changed the title Release 2025.3.1 backmerge Release 2025.3.2 backmerge Jan 15, 2025
@kasperg kasperg merged commit 155253d into develop Jan 15, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants