From: Tom Lane <tgl@sss.pgh.pa.us>
To: marco.lebahn@kfw.de
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19335: the function encrypt does not work correct - ERROR: encrypt error: Key was too big
Date: Thu, 27 Nov 2025 11:01:07 -0500
Message-ID: <126276.1764259267@sss.pgh.pa.us> (raw)
In-Reply-To: <19335-0ba21e6ccf61a219@postgresql.org>
References: <19335-0ba21e6ccf61a219@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> we patched our Systems from 16.10 and 14.19 to the new minor-level 16.11 and
> 14.20.
> No problems with 16.10 and 14.19 while we using the function encrypt and
> decrypt
> After patching the function throws errors
These examples work fine for me in 16.11, and nothing in the
contrib/pgcrypto source code changed between 16.10 and 16.11.
Since pgcrypto depends on OpenSSL, one possible theory is that
your new pgcrypto.so was built against a different version of
OpenSSL than what is installed on your machine. But with no
info about how you did the update, that's only wild speculation.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, marco.lebahn@kfw.de, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19335: the function encrypt does not work correct - ERROR: encrypt error: Key was too big
In-Reply-To: <126276.1764259267@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox