Task #1031 (closed)
Opened 16 years ago
Closed 13 years ago
[DOC] Add VACUUM VERBOSE FULL ANALYZE && REINDEX to upgrade documentation
Reported by: | jamoore | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | OMERO-Beta4.3.1 |
Component: | Deployment | Version: | 3.0-M1 |
Keywords: | postgres, database, performance | Cc: | cxallan |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | n.a. |
Sprint: | 2011-07-07 (1) |
Description (last modified by jmoore)
After a large upgrade, things were a bit slow. A vacuum helped. It might make sense to combine the two since upgrades should be the only time the database is off line. However, putting them in the upgrade scripts makes them non-optional. By adding them to the documentation, users can decide whether or not they want to perform the maintenance tasks.
Change History (8)
comment:1 Changed 15 years ago by jmoore
- Milestone changed from OMERO-Beta4 to OMERO-Beta4.1
comment:2 Changed 15 years ago by jmoore
- Milestone changed from OMERO-Beta4.1 to Future
comment:3 Changed 13 years ago by jmoore
Referencing ticket #2568 has changed sprint.
comment:4 Changed 13 years ago by jmoore
- Description modified (diff)
- Milestone changed from Unscheduled to OMERO-Beta4.3
- Summary changed from Add VACUUM to upgrade scripts to Add VACUUM VERBOSE FULL ANALYZE && REINDEX to upgrade documentation
comment:5 Changed 13 years ago by jmoore
Referencing ticket #2568 has changed sprint.
comment:6 Changed 13 years ago by jmoore
Referencing ticket #2568 has changed sprint.
comment:7 Changed 13 years ago by jmoore
- Owner jmoore deleted
- Summary changed from Add VACUUM VERBOSE FULL ANALYZE && REINDEX to upgrade documentation to [DOC] Add VACUUM VERBOSE FULL ANALYZE && REINDEX to upgrade documentation
comment:8 Changed 13 years ago by jmoore
- Resolution set to fixed
- Status changed from new to closed
Added following to top of server/upgrade:
General HOWTOs Performing a database backup Optimizing an upgraded database (optional) Restoring a database backup if something goes wrong
Can think about this with the other deployment work in 4.1