Re: attribute names & typecast/psql default port - Mailing list pgsql-patches

From Peter Eisentraut
Subject Re: attribute names & typecast/psql default port
Date
Msg-id Pine.LNX.4.30.0109081357010.702-100000@peter.localdomain
Whole thread Raw
In response to attribute names & typecast/psql default port  (Gavin Sherry <swm@linuxworld.com.au>)
Responses Re: attribute names & typecast/psql default port  (Gavin Sherry <swm@linuxworld.com.au>)
List pgsql-patches
Gavin Sherry writes:

> Found this while testing the first patch. As it happens I only have one
> box handy and it was running PG already. I changed the default port to
> 9999. When I executed bin/psql (the freshly built psql) it connected to my
> production postmaster on port 5432.
>
> The patch sets the configured port to that defined in pg_config.h.

I'm not sure I believe that, because I rely on the correct behaviour every
day and I'm sure so do others.  (In fact, your patch would break other
things, such as the PGPORT environment variable.)

The sort of problem you describe is usually caused by psql using the wrong
libpq library (where the default port number is recorded).  I suggest you
run 'ldd psql' to see which one it picks up.

--
Peter Eisentraut   peter_e@gmx.net   http://funkturm.homeip.net/~peter


pgsql-patches by date:

Previous
From: Karel Zak
Date:
Subject: Re: [HACKERS] CURRENT CVS: MULTIBYTE: CANT CONNECT....
Next
From: Rene Pijlman
Date:
Subject: Fix JDBC test suite, set/get transaction isolation level test in ConnectionTest