| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Jim C(dot) Nasby" <decibel(at)decibel(dot)org> |
| Cc: | Joe Conway <mail(at)joeconway(dot)com>, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: Problem with dblink regression test |
| Date: | 2005-06-22 03:21:37 |
| Message-ID: | 22476.1119410497@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
"Jim C. Nasby" <decibel(at)decibel(dot)org> writes:
> It appears that the dblink regression test defaults to port 5432. I've
> been trying to get platypus to compile clean on HEAD and 8_0 and it's
> been failing on dblink.
There are several buildfarm machines failing like this. I think a
possible solution is for the postmaster to do putenv("PGPORT=nnn")
so that libpq instances running in postmaster children will default
to the local installation's actual port rather than some compiled-in
default port.
This is certainly not without its downsides, but if you are running
a postmaster at a nondefault port then I think you ought to be aware
that leaving dblink to choose a default port is a fragile idea.
Thoughts?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2005-06-22 03:26:31 | Re: Problem with dblink regression test |
| Previous Message | Andrew Dunstan | 2005-06-22 03:11:38 | Re: pl/pgsql: END verbosity |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2005-06-22 03:26:31 | Re: Problem with dblink regression test |
| Previous Message | Andrew Dunstan | 2005-06-22 03:11:38 | Re: pl/pgsql: END verbosity |