Re: BUG #1831: plperl gives error after reconnect. - Mailing list pgsql-bugs

From Greg Sabino Mullane
Subject Re: BUG #1831: plperl gives error after reconnect.
Date
Msg-id 89d7c67a17579f0bc64fb432283a010e@biglumber.com
Whole thread Raw
In response to Re: BUG #1831: plperl gives error after reconnect.  (Michael Fuhr <mike@fuhr.org>)
Responses Re: BUG #1831: plperl gives error after reconnect.  (Michael Fuhr <mike@fuhr.org>)
List pgsql-bugs
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> Tom Lane once mentioned that "Valgrind is fairly useless for debugging
> postgres," but has anybody tried it for this problem?  I tried using
> the FreeBSD port but it's having trouble (first I had to hack in
> support for a system call, now it's terminating the postmaster with
> SIBGUS on a call to setproctitle).

I've got valgrind working, but not sure exactly how to use it to debug
this problem. What's the procedure?

- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200508190955
https://www.biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8

-----BEGIN PGP SIGNATURE-----

iEYEARECAAYFAkMF5N8ACgkQvJuQZxSWSsi6eQCggFJT5i9phqGomACJk/ZIKDgS
vv8AnROppubywG9bY2ZU26MMfG3lKPdj
=+srT
-----END PGP SIGNATURE-----

pgsql-bugs by date:

Previous
From: Jorg Heymans
Date:
Subject: importing 0xe3809c character, aka wave dash
Next
From: Tom Lane
Date:
Subject: Re: BUG #1835: pg_trigger_tgrelid_tgname_index