| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Brian Mendoza <brian(at)rotamap(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: JSONB operator unanticipated behaviour |
| Date: | 2023-05-18 15:57:49 |
| Message-ID: | fad1c44c-63d5-d064-cd16-01ffe48abbd8@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 5/18/23 08:46, Tom Lane wrote:
> Brian Mendoza <brian(at)rotamap(dot)net> writes:
>> Ah, yes, that seem to be the explanation!
>> So it would seem that indeed it was my misunderstanding of the operator.
>
> You seem to be reading some fairly old version of the documentation.
> The extended definition that Adrian mentions has been there for
> awhile, but the JSON operator table didn't link to it before v13.
> (I agree that the "top level" bit was just wrong, but it's gone.)
Can you elaborate on gone and/or wrong as I see it in the 15 and devel
documentation.
>
> regards, tom lane
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Owen Stephens | 2023-05-18 16:34:27 | Unexpected cross-database vacuum impact with hot_standby_feedback=on |
| Previous Message | Stephen Frost | 2023-05-18 15:54:31 | Re: Would PostgreSQL 16 native transparent data encryption support database level encryption? |