pg_upgradecluster should use pg_upgrade if available
Bug #939260 reported by
Stuart Bishop
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
postgresql-common (Debian) |
Fix Released
|
Unknown
|
|||
postgresql-common (Ubuntu) |
Triaged
|
Low
|
Unassigned |
Bug Description
A number of new utilities are available in /usr/lib/
pg_basebackup
pg_controldata
pg_resetxlog
maybes:
pg_ctl (may cause too much confusion with existing Debian pg_ctlcluster. Maybe pg_ctlcluster can be deprecated now?)
pg_upgrade (works direct on data directories, so wrapper maybe unsuitable as desired version may not be known. Symlink to pg_upgrade_9.1?)
no longer affects: | postgresql (Ubuntu) |
Changed in postgresql-common (Debian): | |
status: | Unknown → New |
Changed in postgresql-common (Debian): | |
status: | New → Fix Committed |
Changed in postgresql-common (Debian): | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
pg_basebackup was wrapped in postgresql-common 128, which is in precise. pg_controldata, pg_resetxlog, and pg_upgrade are server-side commands and thus are not really adequate for wrapping (only client-side programs are).