From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Peter Geoghegan <pg(at)heroku(dot)com> |
Cc: | Craig Ringer <craig(at)2ndquadrant(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Hannu Krosing <hannu(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Teodor Sigaev <teodor(at)sigaev(dot)ru> |
Subject: | Re: jsonb and nested hstore |
Date: | 2014-02-28 02:08:50 |
Message-ID: | 20140228020850.GS2921@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
* Peter Geoghegan (pg(at)heroku(dot)com) wrote:
> On Thu, Feb 27, 2014 at 6:02 PM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
> > It's also make it a lot harder to use in other extensions, something
> > that's already an issue with hstore.
>
> What do you mean?
Extensions can't depend on other extensions directly- hence you can't
write an extension that depends on hstore, which sucks. It'd be
preferrable to not have that issue w/ json/jsonb/whatever.
Yes, it'd be nice to solve that problem, but I don't see it happening in
the next few weeks...
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2014-02-28 02:09:53 | Re: Auto-tuning work_mem and maintenance_work_mem |
Previous Message | Peter Geoghegan | 2014-02-28 02:04:10 | Re: jsonb and nested hstore |