Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Sun, 23 Mar 2008 18:14:17 +0000
- Message-id: <20080323181417.kss01e5zvkkkk80c@webmail.postgresql.org> <text/plain>
[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.
Michael
- References:
- ECPG connection timeouts
- From: Edmund Bacon
- Re: ECPG connection timeouts
- From: Michael Meskes
- ECPG connection timeouts
- Prev by Date: Re: ECPG connection timeouts
- Previous by thread: Re: ECPG connection timeouts
- Indexes: