pg_upgrade's bindir options could be optional

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: pg_upgrade's bindir options could be optional
Date: 2011-05-06 19:29:44
Message-ID: 1304710184.28821.9.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Just a thought: To make things a bit easier, the bindir options of
pg_upgrade (-b/-B, --old-bindir/--new-bindir) could be made optional, I
think. The new bindir should normally be the one that pg_upgrade itself
is in. And the old bindir could be found out by looking at the
postmaster.opts file in the old data directory. At least by default,
this would make the pg_upgrade invocation a lot more compact; it would
just be: pg_upgrade -d oldir -D newdir.

Comments?

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Browne 2011-05-06 19:30:10 Re: [HACKERS] Re: New Canadian nonprofit for trademark, postgresql.org domain, etc.
Previous Message Magnus Hagander 2011-05-06 19:22:39 Re: Why not install pgstattuple by default?