On May 17, 2016, at 7:58 AM, Jim Nasby <Jim.Nasby@BlueTreble.com> wrote:
> Probably in an attempt to bypass parse overhead on ingestion.
>
> Possibly because JSONB silently eats duplicated keys while JSON doesn't (though in that case even casting to JSONB is
probablynot what you want).
It’s also when you’d want text equivalent semantics.
Best,
David