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

From Gavin Sherry
Subject Re: attribute names & typecast/psql default port
Date
Msg-id Pine.LNX.4.21.0109090234270.25804-100000@linuxworld.com.au
Whole thread Raw
In response to Re: attribute names & typecast/psql default port  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-patches
On Sat, 8 Sep 2001, Peter Eisentraut wrote:

> 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.

It looks that way. My bad - thanks for pointing it out.

Gavin


pgsql-patches by date:

Previous
From: Larry Rosenman
Date:
Subject: Re: [HACKERS] CURRENT CVS: MULTIBYTE: CANT CONNECT....
Next
From: Rene Pijlman
Date:
Subject: Re: [JDBC] [HACKERS] JDBC pg_description update needed for CVS tip