Re: pg_upgrade's bindir options could be optional - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: pg_upgrade's bindir options could be optional
Date
Msg-id 1304729591-sup-6207@alvh.no-ip.org
Whole thread Raw
In response to Re: pg_upgrade's bindir options could be optional  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_upgrade's bindir options could be optional  (Bruce Momjian <bruce@momjian.us>)
Re: pg_upgrade's bindir options could be optional  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
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.

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: Why not install pgstattuple by default?
Next
From: Alvaro Herrera
Date:
Subject: Re: [pgsql-advocacy] New Canadian nonprofit for trademark, postgresql.org domain, etc.