Re: BUG #15789: libpq compilation with OpenSSL 1.1.1b fails on Windows with Visual Studio 2017

From: Sandeep Thakkar <sandeep(dot)thakkar(at)enterprisedb(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com>, serpashk(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15789: libpq compilation with OpenSSL 1.1.1b fails on Windows with Visual Studio 2017
Date: 2019-06-03 10:00:49
Message-ID: CANFyU977NVQCO_Xu_er76Eezg2D3zVNNmf_d7j5d5iq2T6FLdw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, May 31, 2019 at 10:47 PM Michael Paquier <michael(at)paquier(dot)xyz>
wrote:

> On Fri, May 31, 2019 at 04:11:37PM +0200, Juan José Santamaría Flecha
> wrote:
> > Sure, done as [1]. The attached patch is still for 11, will it be back
> > patched?
>
> I don't see a reason why we should not back-patch something like what
> you propose where build with OpenSSL 1.1.0 is supported (aka down to
> 9.5) if that proves to be reliable enough.
>

OpenSSL 1.1.0 and 1.0.2 both are going out of Support in 2019 and PG 9.4 is
supported till Feb2020.
Ideally, 1.1.1x support should be backpatched until 9.4

> --
> Michael
>

--
Sandeep Thakkar

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Wu, Fei 2019-06-03 10:26:05 Typo in execParallel.c
Previous Message PG Bug reporting form 2019-06-03 09:13:15 BUG #15831: pgadmin bug: add column and comment failure when you alter table