Re: pg_config.h.win32 missing a set of flags from pg_config.h.inadded in v11 development
От | Jonathan S. Katz |
---|---|
Тема | Re: pg_config.h.win32 missing a set of flags from pg_config.h.inadded in v11 development |
Дата | |
Msg-id | B87AFDFA-FBBE-415A-859B-6271D8C92A1E@postgresql.org обсуждение исходный текст |
Ответ на | Re: pg_config.h.win32 missing a set of flags from pg_config.h.inadded in v11 development (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: pg_config.h.win32 missing a set of flags from pg_config.h.inadded in v11 development
|
Список | pgsql-hackers |
> On Jun 3, 2018, at 4:29 AM, Michael Paquier <michael@paquier.xyz> wrote: > > On Sat, Jun 02, 2018 at 05:20:57PM -0400, Tom Lane wrote: >> Heikki Linnakangas <hlinnaka@iki.fi> writes: >>> On 02/06/18 17:09, Tom Lane wrote: >>>> More concerning is that RHEL6 is on 1.0.1e: >> >>> I was only thinking of requiring 1.0.2 on Windows. >> >> Ah. Personally, I don't care about that case, but maybe somebody >> else wants to speak for it? > > That's what I meant as well. Cutting the minimal OpenSSL version on > Linux would not come I think without complains so the requirements are > way higher. I know of companies compiling and running benchmarks of > PostgreSQL on past RHEL and SUSE versions, linking to what's locally > available for simplicity. > > A script which reports the version of OpenSSL should be simple enough > for MSVC. And I am ready to bet that at least hamerkop is not using > OpenSSL 1.0.2, so a simple switch would most likely cause the buildfarm > to go red. I am attaching in CC the maintainers of the Windows animals > so as they can comment. Wanted to check in and see if any of the Windows maintainers had thoughts on this issue so we can continue to move it forward. Thanks! Jonathan
В списке pgsql-hackers по дате отправления: