From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | "agharta82(at)gmail(dot)com" <agharta82(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Is OpenSSL AES-NI not available in pgcrypto? |
Date: | 2023-01-07 02:13:42 |
Message-ID: | Y7jVVk6r5roQKiuR@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jan 2, 2023 at 05:57:38PM +0100, agharta82(at)gmail(dot)com wrote:
> So, a test with pgcrypto:
>
> select pgp_sym_encrypt(data::text, 'pwd') --default to aes128
> from generate_series('2022-01-01'::timestamp, '2022-12-31'::timestamp, '1
> hour'::interval) data
>
> vs
>
> select pgp_sym_encrypt(data::text, 'pwd','cipher-algo=bf') -- blowfish
> from generate_series('2022-01-01'::timestamp, '2022-12-31'::timestamp, '1
> hour'::interval) data
To see the difference, I think you need to construct a single large
query that calls many pgcrypto functions, with a small return result, so
the network, parsing, and optimizer overhead are minimal compared to the
OpenSSL overhread.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Embrace your flaws. They make you human, rather than perfect,
which you will never be.
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2023-01-07 02:29:55 | Re: Todo: Teach planner to evaluate multiple windows in the optimal order |
Previous Message | Imseih (AWS), Sami | 2023-01-07 01:59:40 | Re: Add index scan progress to pg_stat_progress_vacuum |