| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Oleg Bartunov <obartunov(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>, Maciek Sakrejda <maciek(at)heroku(dot)com> |
| Subject: | Re: jsonb and nested hstore |
| Date: | 2014-03-10 10:21:19 |
| Message-ID: | CAM3SWZS3gSL3-OVQfDVaJm0m-wgjBPQSue_YbH4xC332xjbO3w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Mar 10, 2014 at 3:19 AM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
> I don't have time to post that at the moment, but offhand I *think*
> your confusion may be due to the fact that the json_hash_ops opclass
> (as I call it) was previously consistent with the behavior of the
> other GIN opclass (the default). The problem is that they (well, at
> least the default GIN and GiST opclasses) were inconsistent with how
> the containment operator behaved in respect of jsonb array elements
> generally.
Sorry, I realize now that that must be incorrect. Still, please take a
look at the commit linked to.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2014-03-10 10:44:59 | Re: jsonb and nested hstore |
| Previous Message | Peter Geoghegan | 2014-03-10 10:19:15 | Re: jsonb and nested hstore |