| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Christophe Pettus <xof(at)thebuild(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: jsonb and nested hstore |
| Date: | 2014-02-28 22:41:22 |
| Message-ID: | CAM3SWZTXOgRNo4dKGp80=TkM89yEeUQ3tn2NGzSLEWiQmPugng@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Feb 28, 2014 at 2:40 PM, Christophe Pettus <xof(at)thebuild(dot)com> wrote:
> On Feb 28, 2014, at 2:12 PM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
>
>> AFAICT, we have these
>> operator classes that work fine with jsonb for the purposes of
>> hstore-style indexing (the hstore operator classes).
>
> That assumes that it is acceptable that jsonb be packaged in the hstore extension. To put it mildly, there's no consensus on that point; indeed, I think there's consensus that's a non-starter.
No, it assumes nothing at all. It's a very simple question.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kohei KaiGai | 2014-03-01 00:00:25 | Re: Custom Scan APIs (Re: Custom Plan node) |
| Previous Message | Christophe Pettus | 2014-02-28 22:40:27 | Re: jsonb and nested hstore |