From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Christophe Pettus <xof(at)thebuild(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: jsonb and nested hstore |
Date: | 2014-02-28 19:46:18 |
Message-ID: | 16721.1393616778@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Josh Berkus <josh(at)agliodbs(dot)com> writes:
> ... This requires larger changes to the existing patch, which likely means
> missing the bus for 9.4 (and you've seen my blog about that)
Yeah. I realize you're gung-ho about getting jsonb into 9.4 in some
form, and I recognize that getting better JSON support is important.
But I wonder how carefully you've thought about the damage it'll do
if what ships in 9.4 is a weird, hard-to-use mishmash. I'd much
rather see us take the time to get it right than to ship something
that's basically a kluge. And having a core type that depends on
an extension for critical functionality is certainly nothing but a
kluge. As an example, you're arguing that some sysadmins won't permit
installation of contrib modules. (Let's pass over the question of
how true or sane that is.) If they won't allow hstore to be installed,
and jsonb is crippled in consequence, where does that put us for
adoption purposes? I'd argue that it's worse than not shipping jsonb
yet at all.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2014-02-28 19:57:15 | Re: jsonb and nested hstore |
Previous Message | Andrew Dunstan | 2014-02-28 19:45:29 | Re: jsonb and nested hstore |