Re: attribute names & typecast/psql default port

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>
Cc: <pgsql-patches(at)postgresql(dot)org>
Subject: Re: attribute names & typecast/psql default port
Date: 2001-09-08 12:03:32
Message-ID: Pine.LNX.4.30.0109081357010.702-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)gmx(dot)net http://funkturm.homeip.net/~peter

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Rene Pijlman 2001-09-08 14:16:04 Fix JDBC test suite, set/get transaction isolation level test in ConnectionTest
Previous Message Karel Zak 2001-09-08 10:50:47 Re: CURRENT CVS: MULTIBYTE: CANT CONNECT....