| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: OpenSSL 3.0.0 compatibility |
| Date: | 2020-07-13 07:40:25 |
| Message-ID: | 7d44559a-5db1-1bbb-0419-eb14c74f2488@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-07-07 22:52, Daniel Gustafsson wrote:
>>> where would be a good place to define
>>> OPENSSL_API_COMPAT? The only place that's shared between frontend and
>>> backend code is c.h. The attached patch does it that way.
>> pg_config_manual.h, perhaps?
> I don't have a strong preference. When starting hacking on this I went for the
> quick and simple option of adding it to CFLAGS in configure.in for the time
> being since I wasn't sure where to put it.
Actually, it would be most formally correct to set it using AC_DEFINE in
configure.in, so that configure tests see it. It doesn't look like we
currently have any configure tests that would really be affected, but it
seems sensible to do it there anyway.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2020-07-13 07:56:29 | Re: Don't choke on files that are removed while pg_rewind runs. |
| Previous Message | Amit Langote | 2020-07-13 07:34:46 | Re: [PATCH] Performance Improvement For Copy From Binary Files |