Re: openssl valgrind failures on skink are due to openssl issue

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: openssl valgrind failures on skink are due to openssl issue
Date: 2019-06-11 20:55:28
Message-ID: 24927.1560286528@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)anarazel(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message legrand legrand 2019-06-11 21:02:47 Re: Adaptive query optimization
Previous Message Andres Freund 2019-06-11 20:51:31 openssl valgrind failures on skink are due to openssl issue