| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Gregory Stark <gsstark(at)mit(dot)edu> |
| Subject: | Re: pgxs problem |
| Date: | 2006-07-19 22:42:25 |
| Message-ID: | 200607200042.26410.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > Yes, that's pretty small-minded. It should be something like
> > PG_CONFIG = pg_config
> > bindir := $(shell $(PG_CONFIG) --bindir)
> > That way you can override it.
>
> No objection here, although I'm not entirely convinced why anyone
> would prefer doing that to setting their PATH. If the pg_config you
> want isn't (first in) your PATH, none of the other PG programs will
> be either, which seems like an awkward situation for getting any
> PG-related work done.
Well, with the above change, both camps would be happy.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-07-19 23:00:40 | Re: How does the planner deal with multiple possible indexes? |
| Previous Message | Andrew Dunstan | 2006-07-19 22:40:22 | Re: plPHP and plRuby |