| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Transparent column encryption |
| Date: | 2022-10-06 14:25:51 |
| Message-ID: | 8458327b-c7be-11b6-ebc1-32798ebf47fa@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 02.10.22 09:16, Andres Freund wrote:
> On 2022-09-27 15:51:25 +0200, Peter Eisentraut wrote:
>> Updated version with meson build system support added (for added files and
>> new tests).
>
> This fails on windows: https://cirrus-ci.com/task/6151847080624128
>
> https://api.cirrus-ci.com/v1/artifact/task/6151847080624128/testrun/build/testrun/column_encryption/001_column_encryption/log/regress_log_001_column_encryption
>
> psql error: stderr: 'OPENSSL_Uplink(00007FFC165CBD50,08): no OPENSSL_Applink'
What in the world is that about? What scant information I could find
suggests that it has something to do with building a "release" build
against an "debug" build of the openssl library, or vice versa. But
this patch doesn't introduce any use of openssl that we haven't seen before.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2022-10-06 14:28:15 | Re: request clarification on pg_restore documentation |
| Previous Message | houzj.fnst@fujitsu.com | 2022-10-06 14:21:10 | RE: Perform streaming logical transactions by background workers and parallel apply |