Re: openssl valgrind failures on skink are due to openssl issue - Mailing list pgsql-hackers

From Andres Freund
Subject Re: openssl valgrind failures on skink are due to openssl issue
Date
Msg-id 20190618233407.ffndfzs2a2l3ovwa@alap3.anarazel.de
Whole thread Raw
In response to Re: openssl valgrind failures on skink are due to openssl issue  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: openssl valgrind failures on skink are due to openssl issue
List 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



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: ANALYZE: ERROR: tuple already updated by self
Next
From: Justin Pryzby
Date:
Subject: Re: ANALYZE: ERROR: tuple already updated by self