On Wed, Jul 31, 2024 at 1:26 PM Robert Haas <robertmh...@gmail.com> wrote: > However, the risk is that an end-user is going to be much less able to > evaluate what is and isn't safe than we are. I think some people are > going to be like -- well the core project doesn't mark enough stuff > leakproof, so I'll just go add markings to a bunch of stuff myself. > And they probably won't stop at stuff like UPPER which is almost > leakproof. They might add it to stuff such as LIKE which results in > immediately giving away the farm. By not giving people any guidance, > we invite them to make up their own rules.
+1. Would it provide enough value for effort to explicitly mark leaky procedures as such? Maybe that could shrink the grey area enough to be protective? --Jacob
