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

From Peter Eisentraut
Subject pg_upgrade's bindir options could be optional
Date
Msg-id 1304710184.28821.9.camel@vanquo.pezone.net
Whole thread Raw
Responses Re: pg_upgrade's bindir options could be optional  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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?




pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Why not install pgstattuple by default?
Next
From: Christopher Browne
Date:
Subject: Re: Re: [pgsql-advocacy] New Canadian nonprofit for trademark, postgresql.org domain, etc.