| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michael Meskes <meskes(at)postgresql(dot)org>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: ECPG could not connect to the database. |
| Date: | 2001-01-08 17:20:42 |
| Message-ID: | Pine.LNX.4.30.0101081818300.760-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tom Lane writes:
> > Not exactly. It is possible to use PGHOST but you also can add the hostname
> > to the dbname.
>
> Have you tried it lately? I suspect that you are depending on code that
> is not in libpq's current sources anymore. I fully agree with Peter E's
> reasons for removing it, too. We do not need to overload the definition
> of libpq's dbname parameter.
Ouch, it *is* documented in ecpg(1). I guess if ecpg wants to provide
this syntax (which it probably should, since the "sql connect to" syntax
doesn't have any other provisions for host name, port, etc.) then it could
take the code from libpq (it's still in there I think) and do the parsing
before calling PQsetdbLogin().
--
Peter Eisentraut peter_e(at)gmx(dot)net http://yi.org/peter-e/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-01-08 17:31:57 | Re: ECPG could not connect to the database. |
| Previous Message | Mikheev, Vadim | 2001-01-08 17:19:30 | RE: backend corruption |