From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_upgrade's bindir options could be optional |
Date: | 2011-05-07 20:55:49 |
Message-ID: | 1304801749.15989.10.camel@vanquo.pezone.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On fre, 2011-05-06 at 21:54 -0300, Alvaro Herrera wrote:
> Excerpts from Tom Lane's message of vie may 06 17:11:35 -0300 2011:
>
> > As an example, the proposed defaults would be not only wrong, but
> > disastrous in the perfectly-reasonable situation where the user has
> > moved the old installation aside and then installed the new
> executables
> > in the same place the old ones used to be. My current RPM packaging
> of
> > pg_upgrade would be at risk for the same reason.
>
> Eh, disastrous? Don't we check the versions reported by each
> postmaster before attempting to do anything? Because if we do, the
> worst that would happen is that the user gets a version mismatch
> error.
> And if we don't ... well, we should.
Yeah, we'd obviously have to decorate that with some checks and error
reporting. But AFAICT we only use the old bindir for running
pg_controldata, so what could go wrong(tm).
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2011-05-07 21:02:34 | Re: pg_upgrade's bindir options could be optional |
Previous Message | Joshua Berkus | 2011-05-07 20:51:45 | Re: [HACKERS] Re: New Canadian nonprofit for trademark, postgresql.org domain, etc. |