| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | 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 04:07:45 |
| Message-ID: | 530D6891.9010206@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2014-02-26 04:22:21 | Re: Custom Scan APIs (Re: Custom Plan node) |
| Previous Message | Kyotaro HORIGUCHI | 2014-02-26 04:02:05 | Re: Get more from indices. |