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

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

Hi,

On 2019-06-18 19:25:12 -0400, Tom Lane wrote:
> Did you get any sense of how fast the openssl fix is goinng to show up?

It's merged to both branches that contain the broken code. Now we need
to wait for the next set of openssl releases, and then for distros to
pick that up. Based on the past release cadence
https://www.openssl.org/news/openssl-1.1.1-notes.html
that seems to be likely to happen within 2-3 months.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2019-06-18 23:48:58 Re: ANALYZE: ERROR: tuple already updated by self
Previous Message Andres Freund 2019-06-18 23:30:33 Re: ANALYZE: ERROR: tuple already updated by self