Re: pgsql: Refactor MD5 implementations according to new cryptohash infrast

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Refactor MD5 implementations according to new cryptohash infrast
Date: 2020-12-10 03:59:30
Message-ID: X9GdIu7QsbrBouXe@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Thu, Dec 10, 2020 at 12:18:57PM +0900, Michael Paquier wrote:
> And this has broken uuid-ossp. The switch is quite easy to do as this
> module just needs to use cryptohash APIs for MD5. Will fix in a
> minute..

So, I have reproduced the failure with --with-uuid=e2fs and now fixed
it with 525e60b.

FWIW, I got to wonder this morning whether we should have a sha1
option for cryptohash.c, and seeing how ugly is the dependency on
md5.c and sha1.c between pgcrypto and uuid-ossp, this may give an
extra reason to do so..
--
Michael

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Alexander Korotkov 2020-12-11 01:51:42 Re: pgsql: Support subscripting of arbitrary types, not only arrays.
Previous Message Michael Paquier 2020-12-10 03:53:46 pgsql: Fix compilation of uuid-ossp