> On 11 Oct 2024, at 00:28, Tom Lane <t...@sss.pgh.pa.us> wrote: > On the whole I agree with Heikki's comment that we should just > do it (disallow MD5, full stop) whenever we feel that enough > time has passed. These intermediate states are mostly going to > add headaches. Maybe we could do something with an intermediate > release that just emits warnings, without any feature changes.
+1, warnings and ample documentation for how to perform the migration (and why, I'm sure it will come as a surprise to *many*) is likely our best investment. That coupled with a well communicated point in time for when MD5 goes away with notices in all release notes up until that point. -- Daniel Gustafsson
