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 1pzg0z-00054K-BV for pgsql-general@arkaria.postgresql.org; Thu, 18 May 2023 15:58:05 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pzg0y-0001LP-2Y for pgsql-general@arkaria.postgresql.org; Thu, 18 May 2023 15:58:04 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pzg0w-0001L5-H7 for pgsql-general@lists.postgresql.org; Thu, 18 May 2023 15:58:03 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pzg0m-000YfG-BU for pgsql-general@postgresql.org; Thu, 18 May 2023 15:58:01 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 198205C0193; Thu, 18 May 2023 11:57:51 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Thu, 18 May 2023 11:57:51 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm3; t= 1684425471; x=1684511871; bh=pcXfSeEOrZWpLmT+UkAoNw4yzVHyWAdo93u YML5VPlI=; b=Jwq4pOA9RtL5HqqYjgSEGfvb/IU2zAsSiznAvTRJDylyDk0xgoM 04jppAiQdBbvWCgDmjJvhzJw4xRGjgfauFA3VfPj3JYSenhbwFZVygPICu6sctZe s4iPoSuszL7NtHHj9D6YdncLc9mXFOlPLp91saMXxt5y/wqBGrg3ab3xJiw5FH2Q fSkhWuvLqyCRTEORVsne9bfXHTROi2aPrd45adEseh6JL37rhrqimaNmmhzEvK/J wf4/altldvwI0wdsgFbJAokFAZ0c7ci0uwFXvqqSJPG1JxBRPJ3C6yuywHYZ5b3v GljlutR2IWUutMl8Tcl7DHeLuzZupNfjVtg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1684425471; x=1684511871; bh=pcXfSeEOrZWpLmT+UkAoNw4yzVHyWAdo93u YML5VPlI=; b=VvAhWFjRABUnH2Cprp5kWyOP85eC57t/39KRytq/JSe4TrjcYVH 44vyGOpUAs7Fg+Hz+Pr4D1KEUgm+0PemG2aocnoeLkRcSfqPYv4A264jB4QXtTwb pouZVgDl2xULNH6DuY48jwCUKc/AyIwiSj8q4wNM9TkL1VHKGVHCLEpOqWPmMRCY MS+tst6Fx8EEC1KA6Jvb/KLUsYDSlOTikbFKEROlGO+sQkfYGaXcV1gagycKOQ5b +365+CcMfHxc4S/TuWGlTbZ3cka8L3y61FxNh0mkCFUR32cHp8yO/knz7C6qJPKe oAlFNsGNLdIQIPmL6sC1uOMD9DQiQhNbwug== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeeifedgleehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpeetughr ihgrnhcumfhlrghvvghruceorggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtg homheqnecuggftrfgrthhtvghrnhepjeegtdfhuefhtefgffdvheduleetgeejudevffek teegjeeiheeuudellefgffffnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpe hmrghilhhfrhhomheprggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 18 May 2023 11:57:50 -0400 (EDT) Message-ID: Date: Thu, 18 May 2023 08:57:49 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.1 Subject: Re: JSONB operator unanticipated behaviour Content-Language: en-US To: Tom Lane , Brian Mendoza Cc: pgsql-general@postgresql.org References: <3802023.1684424813@sss.pgh.pa.us> From: Adrian Klaver In-Reply-To: <3802023.1684424813@sss.pgh.pa.us> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 5/18/23 08:46, Tom Lane wrote: > 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.) Can you elaborate on gone and/or wrong as I see it in the 15 and devel documentation. > > regards, tom lane -- Adrian Klaver adrian.klaver@aklaver.com