Date: Fri, 6 Jan 2023 21:13:42 -0500
From: Bruce Momjian <bruce@momjian.us>
To: "agharta82@gmail.com" <agharta82@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: Is OpenSSL AES-NI not available in pgcrypto?
Message-ID: <Y7jVVk6r5roQKiuR@momjian.us>
References: <6d0809a6-b8f7-4d53-0d2d-07f29a1288bd@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6d0809a6-b8f7-4d53-0d2d-07f29a1288bd@gmail.com>
Archived-At: <https://www.postgresql.org/message-id/Y7jVVk6r5roQKiuR%40momjian.us>
Precedence: bulk

On Mon, Jan  2, 2023 at 05:57:38PM +0100, agharta82@gmail.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@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

Embrace your flaws.  They make you human, rather than perfect,
which you will never be.