| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Use OpenSSL-specific ifdefs in sha2.h |
| Date: | 2019-06-14 00:10:41 |
| Message-ID: | E1hbZnl-0004pN-E1@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Use OpenSSL-specific ifdefs in sha2.h
In order to separate OpenSSL's SHA symbols, this header has been using
USE_SSL, which is equivalent to USE_OPENSSL. There is now only one SSL
implementation included in the tree, so this works fine, but when
adding a new SSL implementation this would run into failures.
Author: Daniel Gustafsson
Discussion: https://postgr.es/m/0DF29010-CE26-4F51-85A6-9C8ABF5536F9@yesql.se
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/96719e52b1abd3a8c712d06a809b7e6c97c2e3a0
Modified Files
--------------
src/include/common/sha2.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2019-06-14 00:27:30 | Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock |
| Previous Message | Tatsuo Ishii | 2019-06-13 22:32:29 | Re: pgsql: Avoid spurious deadlocks when upgrading a tuple lock |