Timeline for MySQL 5.6 to 5.7 In-Place Upgrade or Fresh Install?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 14, 2017 at 18:46 | answer | added | Dave Rix | timeline score: 2 | |
| Jun 3, 2017 at 3:07 | comment | added | 1234567 | @RickJames - right, my concern is just whether to trust it or not. I've never liked doing operating system upgrades... always preferred to reinstall from scratch. Correction to my previous statement: once you finish testing the process on a snapshot, you can perform the upgrade normally on the regular instance (they don't automate this "testing" process for you). | |
| Jun 2, 2017 at 21:57 | comment | added | Rick James | I suggest that AWS has designed the "best" way for their Cloud. (No, I cannot directly vouch for them.) | |
| Jun 2, 2017 at 14:08 | comment | added | 1234567 | @RickJames They allow you to create a snapshot and restore the snapshot to a new 5.7 instance directly. Once you are satisfied, they will perform the actual upgrade on the real instance. | |
| Jun 2, 2017 at 13:59 | comment | added | Rick James | Does AWS keep the 5.6 instance until you say you are happy with the 5.7? | |
| Jun 2, 2017 at 10:44 | history | edited | Paul White♦ | edited tags | |
| Jun 2, 2017 at 6:47 | review | Close votes | |||
| Jun 2, 2017 at 10:44 | |||||
| Jun 2, 2017 at 3:47 | answer | added | Mannoj | timeline score: 3 | |
| Jun 1, 2017 at 23:18 | review | First posts | |||
| Jun 2, 2017 at 6:27 | |||||
| Jun 1, 2017 at 23:17 | history | asked | 1234567 | CC BY-SA 3.0 |