Skip site navigation (1) Skip section navigation (2)

Re: ECPG connection timeouts

From: meskes(at)postgresql(dot)org
To: Michael Meskes <meskes(at)postgresql(dot)org>
Cc: Edmund Bacon <edmund(dot)bacon(at)devstudios(dot)com>,pgsql-interfaces(at)postgresql(dot)org
Subject: Re: ECPG connection timeouts
Date: 2008-03-23 18:14:17
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
[Answering my own email ...]

Zitat von Michael Meskes <meskes(at)postgresql(dot)org>:
> However, you will notice that this doesn't work as I just found that the
> parser doesn't like the "=14" part. I will fix this in a minute.

Need to step backward a little bit. Fixing the parser was easy, but  
apparently PQsetdbLogin does not really set the option correctly.  
Before looking for the bug which might be a formatting problem in ecpg  
but appears to be a PQsetdbLogin limitation I think I better spend the  
time upgrading to use PQconnectDB instead.

BTW shouldn't setting PGOPTIONS (?) accordingly work too? Not sure  
after seeing PQsetdbLogin fail.


In response to

pgsql-interfaces by date

Next:From: Charles SeatonDate: 2008-04-06 23:58:57
Subject: libpq query length limit
Previous:From: Michael MeskesDate: 2008-03-23 17:34:10
Subject: Re: ECPG connection timeouts

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group