From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Michael Meskes <meskes(at)postgresql(dot)org> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: ECPG could not connect to the database. |
Date: | 2001-01-08 08:35:04 |
Message-ID: | 13887.978942904@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Michael Meskes <meskes(at)postgresql(dot)org> writes:
> On Sun, Jan 07, 2001 at 02:52:07PM -0500, Tom Lane wrote:
>> I do not see how that can be ecpg's fault --- it just does
>>
>> this->connection = PQsetdbLogin(NULL, NULL, NULL, NULL, dbname, user, passwd);
>>
>> which means that any specification of the host must come from the PGHOST
>> environment variable and will be handled entirely inside libpq.
> 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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | hubert depesz lubaczewski | 2001-01-08 08:38:50 | functions returning multiple rows? |
Previous Message | Michael Meskes | 2001-01-08 08:06:24 | Re: ECPG could not connect to the database. |