From: Tom Lane <tgl@sss.pgh.pa.us>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Improve error handling of cryptohash computations
Date: Thu, 13 Jan 2022 14:52:12 -0500
Message-ID: <3214611.1642103532@sss.pgh.pa.us> (raw)
In-Reply-To: <9f0c0a96d28cf14fc87296bbe67061c14eb53ae8.camel@cybertec.at>
References: <E1n75SS-0005ck-Oh@gemulon.postgresql.org>
<9f0c0a96d28cf14fc87296bbe67061c14eb53ae8.camel@cybertec.at>
Laurenz Albe <laurenz.albe@cybertec.at> writes:
> On Tue, 2022-01-11 at 00:56 +0000, Michael Paquier wrote:
>> Improve error handling of cryptohash computations
> This commit changes the signature of the exported "pg_md5_hash" function,
> which breaks my extension that uses this function.
> Is there no way to avoid this API break in the back branches?
Probably none of this should have been back-patched --- the issues
are not so large that they require a risk of breaking things in
the back branches.
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us, laurenz.albe@cybertec.at, michael@paquier.xyz
Subject: Re: pgsql: Improve error handling of cryptohash computations
In-Reply-To: <3214611.1642103532@sss.pgh.pa.us>
References: <E1n75SS-0005ck-Oh@gemulon.postgresql.org> <9f0c0a96d28cf14fc87296bbe67061c14eb53ae8.camel@cybertec.at> <3214611.1642103532@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