Re: Problem with dblink regression test

Поиск
Список
Период
Сортировка
От Andrew Dunstan
Тема Re: Problem with dblink regression test
Дата
Msg-id 3614.24.211.165.134.1119410791.squirrel@www.dunslane.net
обсуждение исходный текст
Ответ на Re: Problem with dblink regression test  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Problem with dblink regression test  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Problem with dblink regression test  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Tom Lane said:
> "Jim C. Nasby" <decibel@decibel.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.
>

This seems to be my day for getting confused.

If this diagnosis were correct, wouldn't every buildfarm member be failing
at the ContribCheck stage (if they get that far)? They all run on non
standard ports and all run the contrib installcheck suite if they can (this
is required, not optional). So if they show OK then they do not exhibit the
problem.

Also, while the PGPORT=nnnn trick looks sort of OK, we need to check it will
work on Windows - I am far from sure it will.

cheers

andrew






В списке pgsql-hackers по дате отправления:

Предыдущее
От: Rod Taylor
Дата:
Сообщение: Re: pg_terminate_backend idea
Следующее
От: "Marc G. Fournier"
Дата:
Сообщение: Re: Server instrumentation patch