* Tom Lane wrote:
> Karsten Desler <[EMAIL PROTECTED]> writes:
> > * Bruce Momjian wrote:
> >> I think what you are seeing is that the getaddrinfo memory is placed in
> >> the PGconn structure that isn't freed until PQclear is called. Does
> >> your test call PQclear()?
>
> > s/PQclear/PQfinish/
Karsten Desler <[EMAIL PROTECTED]> writes:
> * Bruce Momjian wrote:
>> I think what you are seeing is that the getaddrinfo memory is placed in
>> the PGconn structure that isn't freed until PQclear is called. Does
>> your test call PQclear()?
> s/PQclear/PQfinish/
> It does call PQclear on the re
* Bruce Momjian wrote:
> I think what you are seeing is that the getaddrinfo memory is placed in
> the PGconn structure that isn't freed until PQclear is called. Does
> your test call PQclear()?
s/PQclear/PQfinish/
It does call PQclear on the result, and PQfinish on the connection.
The code is at
Karsten Desler wrote:
> * Karsten Desler wrote:
> > * Bruce Momjian wrote:
> > > Yes, please --- the patch is at:
> > >
> > > http://archives.postgresql.org/pgsql-patches/2005-06/msg00486.php
> >
> > Thanks.
> > I've applied the patch now, and I'll keep you posted.
>
> It doesn't seem to have
* Karsten Desler wrote:
> * Bruce Momjian wrote:
> > Yes, please --- the patch is at:
> >
> > http://archives.postgresql.org/pgsql-patches/2005-06/msg00486.php
>
> Thanks.
> I've applied the patch now, and I'll keep you posted.
It doesn't seem to have helped, and while poking around a little
* Bruce Momjian wrote:
> Yes, please --- the patch is at:
>
> http://archives.postgresql.org/pgsql-patches/2005-06/msg00486.php
Thanks.
I've applied the patch now, and I'll keep you posted.
Best regards,
Karsten Desler
---(end of broadcast)
Yes, please --- the patch is at:
http://archives.postgresql.org/pgsql-patches/2005-06/msg00486.php
---
Tom Lane wrote:
> "Karsten Desler" <[EMAIL PROTECTED]> writes:
> > I've got a pretty flaky tcpip connection to a
"Karsten Desler" <[EMAIL PROTECTED]> writes:
> I've got a pretty flaky tcpip connection to a Postgres 7.4.7 database server
> and often times (once or twice a day) my program gets stuck in an endless
> busy-loop in PGconnectdb.
Hmm. Maybe you have a test case for the proposed patch for bug #1467?
The following bug has been logged online:
Bug reference: 1736
Logged by: Karsten Desler
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.7
Operating system: debian sarge
Description:endless loop in PQconnectdb
Details:
I've got a pretty flaky tcpip connectio
