Andres Freund <and...@anarazel.de> writes: > On 2022-08-23 13:28:50 -0400, Tom Lane wrote: >> I agree with the upthread comments that we only need/want to catch >> foreseeable incorrect-input errors, and that the way to make that >> happen is to refactor the related type input functions, and that >> a lot of the heavy lifting for that has been done already.
> I think it's a good direction to go in. What of the heavy lifting for that has > been done already? I'd have guessed that the hard part is to add different, > optional, type input, type coercion signatures, and then converting a lot of > types to that? I was assuming that we would only bother to do this for a few core types. Of those, at least the datetime types were already done for previous JSON-related features. If we want extensibility, then as Robert said there's going to have to be work done to create a common API that type input functions can implement, which seems like a pretty heavy lift. We could get it done for v16 if we start now, I imagine. regards, tom lane