Actions
Bug #15416
closed
Bug #15413: Autovacuum may never finish, or take more than one day, on busy Rudder instance, because of resources attrition
Create migration script to remove autovacuum for ruddersysevents
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Error - Fixed
Regression:
Updated by Nicolas CHARLES over 5 years ago
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
Updated by Nicolas CHARLES over 5 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-packages/pull/2023
Updated by Nicolas CHARLES about 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-packages|b74cb9058dbc5a0e9d1c391a4613b6ecb5dc8cc4.
Updated by François ARMAND about 5 years ago
- Subject changed from Create migration script for parent ticket to Create migration script to remove autovacuum for ruddersysevents
Updated by François ARMAND about 5 years ago
- Fix check changed from To do to Error - Blocking
File "dbMigration-5.0.x-5.0.13-remove-autovacuum-on-ruddersysevents.sql" is missing
Updated by François ARMAND about 5 years ago
- Fix check changed from Error - Blocking to Error - Fixed
Updated by Vincent MEMBRÉ about 5 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.13 which was released today.
Actions