| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | obartunov(at)gmail(dot)com |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: jsonb and nested hstore |
| Date: | 2014-03-04 09:43:49 |
| Message-ID: | CAM3SWZQTuzjWiZQDzBiBajak+dsSVafZmhB-m2fvfE+17P8yaw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 4, 2014 at 1:30 AM, Oleg Bartunov <obartunov(at)gmail(dot)com> wrote:
> Thanks, looks like a bug.
I guess this is down to the continued definition of gin_hstore_ops as
an opclass with text storage?:
+ CREATE OPERATOR CLASS gin_hstore_ops
+ DEFAULT FOR TYPE hstore USING gin
+ AS
+ OPERATOR 7 @>,
+ OPERATOR 9 ?(hstore,text),
+ OPERATOR 10 ?|(hstore,text[]),
+ OPERATOR 11 ?&(hstore,text[]),
+ FUNCTION 1 bttextcmp(text,text),
+ FUNCTION 2 gin_extract_hstore(internal, internal),
+ FUNCTION 3 gin_extract_hstore_query(internal,
internal, int2, internal, internal),
+ FUNCTION 4 gin_consistent_hstore(internal, int2,
internal, int4, internal, internal),
+ STORAGE text;
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Atri Sharma | 2014-03-04 09:51:40 | Re: ALTER TABLE lock strength reduction patch is unsafe |
| Previous Message | KONDO Mitsumasa | 2014-03-04 09:38:01 | Re: Add min and max execute statement time in pg_stat_statement |