Hi > I could get behind fixing > it to always throw the error, but that's not what Sergei was hoping for. On the contrary i think it is reasonable way. It is much better to have error on input value instead of finding wrong value during table processing. We always reject this value for jsonb and i expected the same behavior for json. Not sure about JSON specification compliance, didn't find anything about \u0000 in rfc8259.
regards, Sergei
