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. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
