pg_regress.sh overrides PGPORT

Started by Tatsuo Ishiiabout 24 years ago3 messages
#1Tatsuo Ishii
t-ishii@sra.co.jp

Does anybody know why test/regress/pg_regress.sh overrides --port or
PGPORT? It would be nice if we could do two distinct tests at the same
time. But pg_regress.sh forces to use port 65432.
--
Tatsuo Ishii

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Tatsuo Ishii (#1)
Re: pg_regress.sh overrides PGPORT

Tatsuo Ishii <t-ishii@sra.co.jp> writes:

Does anybody know why test/regress/pg_regress.sh overrides --port or
PGPORT? It would be nice if we could do two distinct tests at the same
time. But pg_regress.sh forces to use port 65432.

Well, it should surely *not* use PGPORT; that's likely to be occupied.
But a --port switch doesn't seem unreasonable.

regards, tom lane

#3Bruce Momjian
pgman@candle.pha.pa.us
In reply to: Tom Lane (#2)
Re: pg_regress.sh overrides PGPORT

Tatsuo Ishii <t-ishii@sra.co.jp> writes:

Does anybody know why test/regress/pg_regress.sh overrides --port or
PGPORT? It would be nice if we could do two distinct tests at the same
time. But pg_regress.sh forces to use port 65432.

Well, it should surely *not* use PGPORT; that's likely to be occupied.
But a --port switch doesn't seem unreasonable.

Added to TODO:

* Add --port flag to regression tests

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026