On Wed, Aug 8, 2012 at 4:29 PM, Alvaro Herrera <alvhe...@2ndquadrant.com> wrote: > > I wonder if things would be facilitated by having a config file for > pg_upgrade to specify binary and PGDATA paths instead of having awkward > command line switches. That way you could request the user to create > such a file, then >
i like this idea, when i have used pg_upgrade i have been running it several times with --check until everything is ok and then the actual upgrade... so i always create a shell script to run it, a config file should be a good idea > > You could even have a mode on which pg_upgrade asks for the necessary > information to create the config file. For example > > pg_upgrade --create-config=/somewhere/pg_upgrade.conf > Path to new binaries: /usr/local/pg92 > Path to old binaries: /usr/local/pg84 > Path to old data directory: /srv/pgsql-84/data > Path to new data directory: /srv/pgsql-92/data > Use link mode (y/N): n > ... using copy mode. > [now run the checks and complain about missing binaries, etc] > even better -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y capacitación -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
