Re: pg_upgrade's bindir options could be optional

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, 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 21:02:34
Message-ID: 1304802154.15989.16.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On lör, 2011-05-07 at 13:33 -0400, Bruce Momjian wrote:
> Another
> interesting approach would be to assume the /bin directory is ../bin
> from the data directory. That would work for some installs,
> particularly for people moving things around, but again, it is worth
> trying to default something that isn't going to be 100% right?

In practice, there are the two main camps of parallel installation and
move old installation out of the way. They are probably both pretty big
(Debias camp 1, Red Hat is camp 2, for a start). So it would be worth
doing something to help one camp or the other.

On that other hand, we don't have any data on how many people have the
bindir at ../bin from the data directory, or whether it would be the old
or the new bindir.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Smith 2011-05-07 21:06:22 Re: Why not install pgstattuple by default?
Previous Message Peter Eisentraut 2011-05-07 20:55:49 Re: pg_upgrade's bindir options could be optional