On Tue, 28 Oct 2025 at 17:41, Dagfinn Ilmari Mannsåker <[email protected]> wrote: > Here's a patch for that.
Looks good to me. Maybe add a test where not every byte is the same though. > I'm not 100% confident about the error code > for invalid length, but that was the closest one I could find in > errcodes.txt. The errorcode you chose seems acceptable to me, but I think a slightly more fitting option would be ERRCODE_INVALID_BINARY_REPRESENTATION. Error codes in postgres are pretty arbitrary though, so either seems fine to me.
