4 ms·
This isn't as bad as it sounds As someone who has done this multiple times in the past I have to disagree. Yes, it is very much as bad as it sounds and a big
by moe 12y ago
This isn't as bad as it sounds
As someone who has done this multiple times in the past I have to disagree.
Yes, it is very much as bad as it sounds and a big pain point with Postgresql in general and RDS in particular.
For small databases it may be considered a mere nuisance. But when your pg_dump takes an hour to complete then the whole "final sync and cutover" becomes a real problem.
- pilif 12y ago>Yes, it is very much as bad as it sounds and a big pain point with Postgresql in general and RDS in particular. this is pretty much a problem with RDS only. Postgres itself offers pg_upgrade which can do even huge databases (2 TB here) in seconds.
- moe 12y agopg_upgrade which can do even huge databases (2 TB here) in seconds. That depends on various factors. Sometimes pg_upgrade has to copy all your data. In those cases and for 2T you'll be measuring the wait in hours, not seconds.
- saurik 12y agoI am under the impression that the only cases where this happens are when upgrading certain custom data types related to full-text search from 8.3 to 9.x, which seems like a very narrow complaint. This definitely used to be a serious general issue with PostgreSQL, however, but hasn't been in many years.