| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "John Liu" <johnl(at)emrx(dot)com> |
| Cc: | "Christoph Haller" <ch(at)rodos(dot)fzk(dot)de>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: can't create database |
| Date: | 2003-04-03 15:23:38 |
| Message-ID: | 28621.1049383418@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"John Liu" <johnl(at)emrx(dot)com> writes:
> I already set the 2nd port for the new
> installation, otherwise, postmaster will not
> start up ...
But your client-side programs are still talking to the port where the
old postmaster is.
You could set PGPORT in their environment to fix that. What I find more
convenient, though, when I intend to run multiple installations on one
machine, is to build each one with "--with-pgport=XXXX" added to the
configure switches, choosing a different default port XXXX for each.
Then you don't have to worry about switching PGPORT environment (only
about putting the right version of psql first in your path ...)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | pgsql | 2003-04-03 15:44:47 | Re: contrib and licensing |
| Previous Message | Andrew Sullivan | 2003-04-03 15:21:52 | more contrib: log rotator |