Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> On 2/19/18 21:07, Michael Paquier wrote:
>> varlena.c is already large and messy. I would suggest to split into a
>> new file all the user-facing cryptographic functions, including md5 and
>> hex functions, say in src/backend/utils/adt/crypt.c.
> I had originally started a new file called hash.c, but I figured that
> would be quite confusing. I can use crypt.c or a similar name.
> Although crypt.c sounds a lot like crypt().
cryptohashes.c or some such? I concur with Michael that dropping this
into varlena.c isn't a great plan.
regards, tom lane
