Re: jsonb and nested hstore
От | Merlin Moncure |
---|---|
Тема | Re: jsonb and nested hstore |
Дата | |
Msg-id | CAHyXU0zyOpUh_nbB36gHzN=uzg+RwzeSJ3hwkKCfJFCHmkNSGw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: jsonb and nested hstore (Craig Ringer <craig@2ndquadrant.com>) |
Список | pgsql-hackers |
On Tue, Feb 25, 2014 at 10:07 PM, Craig Ringer <craig@2ndquadrant.com> wrote: > On 02/26/2014 06:21 AM, Merlin Moncure wrote: >> On Tue, Feb 25, 2014 at 4:03 PM, Josh Berkus <josh@agliodbs.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
В списке pgsql-hackers по дате отправления: