[pgpool-general: 9065] Re: Segmentation after switchover

Emond Papegaaij emond.papegaaij at gmail.com
Wed Apr 3 15:35:35 JST 2024


>
> Thank you for testing the patch.  I have been looking into the source
> code and have found more places where "volatile" is lacking. I will
> come up with a new patch tomorrow.
>

I ran pgpool with valgrind and got some interesting results you might want
to take a look at. Not only did it report an invalid read at the time of
the segmentation vault, but it also reported quite a few locations where
uninitialized values are being used. I've attached the log. The SIGSEGV is
at timestamp 2024-04-02T23:11:11.254668098Z.

Best regards,
Emond
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pgpool.net/pipermail/pgpool-general/attachments/20240403/a5b76e54/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tkh-pgpool.log
Type: text/x-log
Size: 343534 bytes
Desc: not available
URL: <http://www.pgpool.net/pipermail/pgpool-general/attachments/20240403/a5b76e54/attachment.bin>


More information about the pgpool-general mailing list