From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Teodor Sigaev <teodor(at)sigaev(dot)ru> |
Subject: | Re: jsonb and nested hstore |
Date: | 2014-02-26 14:54:46 |
Message-ID: | CAHyXU0zyOpUh_nbB36gHzN=uzg+RwzeSJ3hwkKCfJFCHmkNSGw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Feb 25, 2014 at 10:07 PM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
> On 02/26/2014 06:21 AM, Merlin Moncure wrote:
>> On Tue, Feb 25, 2014 at 4:03 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>>> On 02/25/2014 12:12 PM, Robert Haas wrote:
>>>> I don't agree that jsonb should be preferred in all but a handful of
>>>> situations. Nor do I agree that partisanship belongs in our
>>>> documentation. Therefore, -1 for your proposal to recommend that, and
>>>> +1 for Merlin's proposal to present a comparison which fairly
>>>> illustrates the situations in which each will outperform the other.
>>>
>>> Awaiting doc patch from Merlin, then. It will need to be clear enough
>>> that an ordinary user can distinguish which type they want.
>>
>> Sure.
>
> Please also highlight that any change will require a full table rewrite
> with an exclusive lock, so data type choices on larger tables may be
> hard to change later.
Yeah. Good idea. Also gonna make a table of what happens when you
cast from A to B (via text, json, jsonb, hstore).
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Sandro Santilli | 2014-02-26 15:01:13 | Re: Uninterruptable regexp_replace in 9.3.1 ? |
Previous Message | Christian Kruse | 2014-02-26 14:25:24 | Re: [PATCH] Use MAP_HUGETLB where supported (v3) |