Thanks for the response. I may have been a bit off in my diagnosis of what was going wrong. My bug report stemmed from the fact that the below returns different results, the first throwing an error and the second returning no rows:
SELECT '{"test":null}'::json->>'test' will return a null SELECT '{"test":null}'::json->'test' will return a string 'null' The 2nd option seems like it should also return a null.
This seems under documented but I can confidently say the behavior shown is intended and thus not a bug. Nor should it be changed. The second example returns a json typed value that when printed as text is the character sequence null. It does not return a PostgreSQL string type.
Conversion of json null to PostgreSQL text results in a NULL of type text, which is indeed the first outcome. This is, however, a lossy one-way conversion since NULL::json is NULL, not ‘null’.
