On 05.03.23 00:04, Tom Lane wrote:
> I've gone through this and have a modest suggestion: let's invent some
> wrapper functions around encode(sha256()) to reduce the cosmetic diffs
> and consequent need for closer study of patch changes. In the attached
> I called them "notmd5()", but I'm surely not wedded to that name.
Do you mean create this on the fly in the test suite, or make it a new
built-in function?
