Re: BUG #1831: plperl gives error after reconnect.
От | Greg Sabino Mullane |
---|---|
Тема | Re: BUG #1831: plperl gives error after reconnect. |
Дата | |
Msg-id | 89d7c67a17579f0bc64fb432283a010e@biglumber.com обсуждение исходный текст |
Ответ на | Re: BUG #1831: plperl gives error after reconnect. (Michael Fuhr <mike@fuhr.org>) |
Ответы |
Re: BUG #1831: plperl gives error after reconnect.
|
Список | 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 по дате отправления: