Re: jsonb contains behaviour weirdness

From: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
To: Peter Geoghegan <pg(at)heroku(dot)com>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: jsonb contains behaviour weirdness
Date: 2014-09-12 20:28:50
Message-ID: CAPpHfdvHc-Dht6i3hSgYYsJAM3GbT0j1xK8Cg3tQ4UXFEKzw6A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Sep 12, 2014 at 10:38 PM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:

> On Fri, Sep 12, 2014 at 11:21 AM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> >> # select '[1,1,2]'::jsonb @> '[1,2,2]'::jsonb;
> >> ?column?
> >> ----------
> >> t
> >> (1 row)
> >>
> >> But, it's not. Jsonb contains takes care only about length of array.
> >
> > OK, now, that's messed up.
>
> To be clear: I don't think that this example is messed up (in
> isolation). I think it's the correct behavior. What I find
> objectionable is the inconsistency. I believe that this is Alexander's
> concern too. Alexander's first example exhibits broken behavior.
>

Agree. I just tried to explain how current behaviour could look for user
who sees it for the first time.

------
With best regards,
Alexander Korotkov.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2014-09-12 20:30:51 Re: jsonb format is pessimal for toast compression
Previous Message Andres Freund 2014-09-12 20:27:49 Re: [REVIEW] Re: Compression of full-page-writes