From: | Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: -Wformat-zero-length |
Date: | 2012-08-08 21:58:33 |
Message-ID: | CAJKUy5j6e68+Wf3Fc+ZhA=EFxTrO==Yn6yOktT9rENaT2VjrXQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Aug 8, 2012 at 4:29 PM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-08-08 22:42:27 | Re: -Wformat-zero-length |
Previous Message | Alvaro Herrera | 2012-08-08 21:29:49 | Re: -Wformat-zero-length |