Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pzgcW-0006Ys-1p for pgsql-general@arkaria.postgresql.org; Thu, 18 May 2023 16:36:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pzgcU-00061x-Ut for pgsql-general@arkaria.postgresql.org; Thu, 18 May 2023 16:36:50 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pzgcU-00061o-K1 for pgsql-general@lists.postgresql.org; Thu, 18 May 2023 16:36:50 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pzgcN-000W9u-M4 for pgsql-general@postgresql.org; Thu, 18 May 2023 16:36:49 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 34IGafXa3853946; Thu, 18 May 2023 12:36:41 -0400 From: Tom Lane To: Adrian Klaver cc: Brian Mendoza , pgsql-general@postgresql.org Subject: Re: JSONB operator unanticipated behaviour In-reply-to: References: <3802023.1684424813@sss.pgh.pa.us> Comments: In-reply-to Adrian Klaver message dated "Thu, 18 May 2023 08:57:49 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3853944.1684427801.1@sss.pgh.pa.us> Date: Thu, 18 May 2023 12:36:41 -0400 Message-ID: <3853945.1684427801@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Adrian Klaver writes: > On 5/18/23 08:46, Tom Lane wrote: >> 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. In v12 (and probably earlier, didn't look) Table 9.45 defines @> as "Does the left JSON value contain the right JSON path/value entries at the top level?" [1]. regards, tom lane [1] https://www.postgresql.org/docs/12/functions-json.html