Re: Remove incidental md5() function uses from several tests

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Remove incidental md5() function uses from several tests
Date: 2023-06-07 08:19:30
Message-ID: CE6D04E6-6CB7-4F83-AA6B-1F51F63D732F@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 7 Jun 2023, at 08:59, Peter Eisentraut <peter(at)eisentraut(dot)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 replaced by 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 repetitive and wouldn't really save much here. In some cases it was easier to remove one layer of indirection by changing column 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Pyhalov 2023-06-07 09:47:01 Re: Partial aggregates pushdown
Previous Message Alexander Lakhin 2023-06-07 08:00:00 Re: Importing pg_bsd_indent into our source tree