Message-ID: <20080323181417.kss01e5zvkkkk80c@webmail.postgresql.org>
Date: Sun, 23 Mar 2008 18:14:17 +0000
From: meskes@postgresql.org
To: Michael Meskes <meskes@postgresql.org>
Cc: Edmund Bacon <edmund.bacon@devstudios.com>,
 pgsql-interfaces@postgresql.org
Subject: Re: ECPG connection timeouts
References: 
 <ABAE5512DA3D4E4597C82947769214380138B9CB@devmail.devstudios.local>
	<20080323173410.GB6560@feivel.credativ.de>
In-Reply-To: <20080323173410.GB6560@feivel.credativ.de>
MIME-Version: 1.0
Content-Type: text/plain;
	charset=ISO-8859-1;
	DelSp="Yes";
	format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.1.2) / FreeBSD-6.1

[Answering my own email ...]

Zitat von Michael Meskes <meskes@postgresql.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.

Michael