len = 5
off = 1633
destsize = 0
__func__ = "pglz_decompress"
--snip
Thanks in advance,
Karsten Desler
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
* Tom Lane wrote:
> Karsten Desler <[EMAIL PROTECTED]> writes:
> > I have a smallish postgres database that segfaults everytime when I try to
> > access a certain row in a certain column.
>
> Looks like a corrupted-data issue to me. It might be interesting to
> dump
* Zdenek Kotala wrote:
> Karsten Desler wrote:
> >
> >I don't know much about the postgres architecture and I don't know if
> >bounds
> >checking on-disk values on a read makes a lot of sense since usually one
> >should be able to assume that there are n
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
* 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
-
* 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 s
called PQexec: 0x80525b8
calling PQclear: 0x80525b8
calling PQfinish: 0x804a008
...
called PQconnectdb: 0x804a008
called PQexec: 0x80525b8
calling PQclear: 0x80525b8
calling PQfinish: 0x804a008
...
and no leaking output from valgrind.
Best regards,
Karsten Desler
#include
#include
// gcc -lpq
* 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
