Andres Freund <andres@anarazel.de> writes:
> For reasons I do not understand the "cosmetic change" was backpatched
> into 1.1.1 And the fix for the cosmetic change, made on master at the
> end of March, was only backpatched to 1.1.1 *after* the 1.1.1c release
> was made in late May. I mean, huh.
Bleah. Not that we've not made equally dumb mistakes :-(
> I can't think of a better way to fix skink for now than just disabling
> openssl for skink, until 1.1.1d is released.
Couldn't you install a local valgrind exclusion matching this stack trace?
regards, tom lane