3 ms·
As with any major postgres update this calls from a full dump of the database and a restore into the new version-you can't simply update the database files. pg
by a2tech 16y ago
As with any major postgres update this calls from a full dump of the database and a restore into the new version-you can't simply update the database files.
pg_dump -clean makes this a snap so you shouldn't have any problems upgrading. (oh and if you're doing backups-you are using pg_dump --clean right? Its really the best way).
- russss 16y agoIf you use "pg_dump -F c", pg_restore is able to parallelize the restore, which makes things go a lot quicker.
- a2tech 16y agoWow-thats a great tip. Thanks!
- pilif 16y agomaybe we'll get an updated pg_migrator once the release is out. While dump/restore is for sure the safer option, once your databases reach Terabytes in size, doing the migration in-place (most of the time the on-disc structure is quite similar between releases) will be a huge speed advantage.
- defen 16y agoDoes this cause any problems if you have foreign key constraints? I remember running into that problem a couple years ago when restoring a pg_dump.