Re: Remove incidental md5() function uses from several tests - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: Remove incidental md5() function uses from several tests
Date
Msg-id CE6D04E6-6CB7-4F83-AA6B-1F51F63D732F@yesql.se
Whole thread Raw
In response to Remove incidental md5() function uses from several tests  (Peter Eisentraut <peter@eisentraut.org>)
Responses Re: Remove incidental md5() function uses from several tests
List pgsql-hackers
> On 7 Jun 2023, at 08:59, Peter Eisentraut <peter@eisentraut.org> wrote:
>
> Continuing the work started with 208bf364a9, this patch removes md5() function calls from these test suites:
>
> - bloom
> - test_decoding
> - isolation
> - recovery
> - subscription
>
> This covers all remaining test suites where md5() calls were just used to generate some random data and can be
replacedby appropriately adapted sha256() calls. 

LGTM from a skim.

> Unlike for the main regression tests, I didn't write a fipshash() wrapper here, because that would have been too
repetitiveand wouldn't really save much here.  In some cases it was easier to remove one layer of indirection by
changingcolumn types from text to bytea. 

Agreed.  Since the commit message mentions 208bf364a9 it would probably be a
good idea to add some version of the above fipshash clarification to the commit
message.

--
Daniel Gustafsson




pgsql-hackers by date:

Previous
From: Alexander Lakhin
Date:
Subject: Re: Importing pg_bsd_indent into our source tree
Next
From: Alexander Pyhalov
Date:
Subject: Re: Partial aggregates pushdown