On 11/19/2013 03:06 PM, Merlin Moncure wrote:
>> Therefore I am interested only in supporting two:
>>
>> a) the legacy behavior from 9.2 and 9.3 so we don't destroy people's
> I'm uncomfortable with the word 'legacy'. This suggests the new type
> will essentially deprecate the old type.
"Existing" might be a better word.
> jsonb will be likely be
> pessimal to large serializations. If you're not manipulating and
> searching the documents, why would you use it? It's going to take
> more space on disk and memory and should provide little benefit for
> present *as well as future code* . (note, it will provide extreme
> benefits for nosql type uses which is of huge strategic importance for
> the project). json and jsonb APIs should work together cleanly, and
> the documentation should suggest which types are different and better
> for which cases.
I agree with most of this.
cheers
andrew
