Peter Eisentraut wrote:
> On Friday 03 July 2009 02:28:22 Bruce Momjian wrote:
> > I looked at that and the problem is that pg_migrator must be built
> > against the _new_ source tree, and will issue an error and exit if it
> > isn't. The problem with PGXS is it silently chooses the source tree to
> > use based on which pg_config it finds in its path first; that seems
> > error-prone. Any ideas for a clearer way to specify pg_config, and is
> > that really helping things if the user has to specify it?
>
> The standard way to do that is
>
> make PG_CONFIG=/some/where/pg84/pg_config
>
> > As you can
> > see, pg_migrator has the requirement of running in a multi-pg_config
> > binary environment, so it has extra complexity that might make pg_config
> > an undesirable option to be promoted first.
>
> It's certainly easier to do the above than having to download, configure, and
> modify the PostgreSQL source tree, I think.
I see you are replying to an old email; the current installer
instrutions are:
(7) Build pg_migrator
For pg_migrator source installs, keep in mind the compile must use the
_new_ PostgreSQL source directory and be installed in the new Postgres
install directory.
The simplest build option is to use PGXS:
gmake USE_PGXS=1 PG_CONFIG=/usr/local/pgsql/bin/pg_config
install
Another option is to point to the top of the new PostgreSQL source tree
by running something like:
gmake top_builddir=/usr/src/pgsql install
Replace '/usr/src/pgsql' with your new source directory. pg_migrator
also understands the 'prefix=' specification if you installed Postgres
in a custom location.
pg_migrator does need a compiled backend source tree to be compiled,
e.g. it needs libpgport and access to backend C defines.
--
Bruce Momjian <[email protected]> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
