Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ejoLV-00006y-1V for pgsql-docs@arkaria.postgresql.org; Thu, 08 Feb 2018 15:42:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ejoLT-0001ET-KK for pgsql-docs@arkaria.postgresql.org; Thu, 08 Feb 2018 15:42:43 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1ejoLT-0001EJ-Eq for pgsql-docs@lists.postgresql.org; Thu, 08 Feb 2018 15:42:43 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ejoLQ-0005YS-Fe for pgsql-docs@postgresql.org; Thu, 08 Feb 2018 15:42:42 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id w18FgYnd025754; Thu, 8 Feb 2018 10:42:34 -0500 From: Tom Lane To: "David G. Johnston" cc: Adrien Nayrat , pgsql-docs@postgresql.org Subject: Re: Text operators "~<=~ ~<~ ~>=~ ~>~" not documented In-reply-to: References: <92d30118-9933-3674-a95b-f84c97abde6c@dalibo.com> Comments: In-reply-to "David G. Johnston" message dated "Thu, 08 Feb 2018 08:32:50 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <25752.1518104554.1@sss.pgh.pa.us> Date: Thu, 08 Feb 2018 10:42:34 -0500 Message-ID: <25753.1518104554@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk "David G. Johnston" writes: > On Thu, Feb 8, 2018 at 6:26 AM, Adrien Nayrat > wrote: >> While reading [1] I notice $subject operators lacks of explanation in >> documentation. > I'd be inclined to remove those four operators from the spgist page's table > and replace them with "LIKE". Then in the text below the table explain > that LIKE is implemented using a combination of those four operators. I believe it's intentional that those operators aren't documented: we don't want people to get in the habit of using them directly. (These days, if you actually need what they do, the approved way to spell it is like 'x < y COLLATE "C"'.) So actually, my inclination would be to remove them from the spgist table and put nothing back. Implying that spgist text_ops fully supports LIKE would certainly be wrong/confusing --- we do not claim in the main part of the docs that btree text_ops supports LIKE, even though it has a comparable level of support as long as you're using C collation. Since these operators are user-visible in EXPLAIN output, there might be merit in mentioning them in passing in the LIKE docs. But we should not put them in a table with the LIKE ops themselves, IMO. That would just invite confusion about what they do and whether you're supposed to use them directly. regards, tom lane