Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#21929 - [postgresql] pg_upgrade database when changing major version

Attached to Project: Arch Linux
Opened by Caleb Cushing (xenoterracide) - Monday, 29 November 2010, 22:09 GMT
Last edited by Dan McGee (toofishes) - Tuesday, 21 June 2011, 22:44 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Paul Mattal (paul)
Dan McGee (toofishes)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

postgres is now capable of upgrading without a dump restore. using pg_upgrade, problem is that both the old binaries and the new binaries have to be on the system, the best time to do this during the software upgrade on arch. I think it'd be possible to run it after the new binaries are unpacked but before they're copied into place. Also I doubt that this will have a negative effect if it's not required... but I'm not 100% on that, so I'm not sure if there's a way to tell and record if we're moving from just minor version to minor version.
This task depends upon

Closed by  Dan McGee (toofishes)
Tuesday, 21 June 2011, 22:44 GMT
Reason for closing:  Implemented
Additional comments about closing:  It is now possible to use this tool, but we aren't going to hold your hand.
Comment by Dan McGee (toofishes) - Tuesday, 21 June 2011, 22:43 GMT
The new postgresql-old-upgrade package should help make this possible on Arch, and I updated the PostgreSQL wiki page a bit.

Loading...