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 1pzfqJ-0004Yi-Qu for pgsql-general@arkaria.postgresql.org; Thu, 18 May 2023 15:47:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pzfqH-00017f-Ok for pgsql-general@arkaria.postgresql.org; Thu, 18 May 2023 15:47:01 +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 1pzfqH-00017W-E1 for pgsql-general@lists.postgresql.org; Thu, 18 May 2023 15:47:01 +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 1pzfqD-000Vnl-Or for pgsql-general@postgresql.org; Thu, 18 May 2023 15:47:00 +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 34IFkr7I3802024; Thu, 18 May 2023 11:46:53 -0400 From: Tom Lane To: Brian Mendoza cc: Adrian Klaver , pgsql-general@postgresql.org Subject: Re: JSONB operator unanticipated behaviour In-reply-to: References: Comments: In-reply-to Brian Mendoza message dated "Thu, 18 May 2023 16:09:22 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3802022.1684424813.1@sss.pgh.pa.us> Date: Thu, 18 May 2023 11:46:53 -0400 Message-ID: <3802023.1684424813@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Brian Mendoza 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.) regards, tom lane