Opened 7 years ago
Closed 5 years ago
#3 closed feature (fixed)
Aggregate and garbage-collect *_log tables.
| Reported by: | mornfall | Owned by: | mornfall |
|---|---|---|---|
| Priority: | major | Milestone: | 5.0 |
| Component: | bench | Keywords: | |
| Cc: |
Description
When the log tables grow too much, they become useless anyway. We can add triggers to automatically aggregate the data, down to a few rows per execution. Full data should be available for a couple of weeks after they were collected.
Change History (3)
comment:1 Changed 7 years ago by
| Type: | defect → feature |
|---|
comment:2 Changed 6 years ago by
| Milestone: | future → 5.0 |
|---|
comment:3 Changed 5 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
The added triggers should do for now, we may want to collect other info from the *_log tables in the future. After update on the 'job' table, the info is collected and any logs older than 2 weeks are removed.
Note: See
TracTickets for help on using
tickets.
Milestone renamed