| << Back to previous view |
|
[QB-3216] Maintenance oF QuickBuild database
|
|
| Status: | Closed |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 8.0.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Phong Trinh | Assigned To: | Robin Shen |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Environment: | Linux | ||
| Description |
|
We are using PostgreSql for our QuickBuild database, and the database is running out of disk spaces sometimes. We have a maintenance job which checks several QuickBuild configurations every 30 minutes to see whether they are as desired. If not, it modifies them. Recently there were some reasons, these configurations were modified every 30 minutes, and this took a lot of disk spaces of the database. Could you please give me recommendations on maintenance of the QuickBuild database?
Thank you in advance, ptrinh |
| Comments |
| Comment by Robin Shen [ 09/Jul/18 11:38 PM ] |
|
This is due to the fact that PostgreSQL does not purge LOBs automatically even if they are no longer being used. I'd suggest to write some form of stored procedure at PostgreSQL side to purge unused LOBs periodically as suggested here:
https://www.postgresql.org/docs/9.1/static/vacuumlo.html |
| Comment by Phong Trinh [ 13/Jul/18 03:04 PM ] |
| Thank you for the suggestion, Robin. |