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 1k30Tp-0003Va-HK for pgsql-bugs@arkaria.postgresql.org; Tue, 04 Aug 2020 17:12:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1k30To-00060V-6C for pgsql-bugs@arkaria.postgresql.org; Tue, 04 Aug 2020 17:12:00 +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 1k30Tn-00060O-TS for pgsql-bugs@lists.postgresql.org; Tue, 04 Aug 2020 17:11:59 +0000 Received: from mail-wm1-x335.google.com ([2a00:1450:4864:20::335]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1k30Tk-00086w-Nb for pgsql-bugs@lists.postgresql.org; Tue, 04 Aug 2020 17:11:58 +0000 Received: by mail-wm1-x335.google.com with SMTP id 184so3680596wmb.0 for ; Tue, 04 Aug 2020 10:11:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to; bh=Y+Tt16laOOXlzdN0sH+EcFV9G9C4nIDUaWnk4FTPJ7s=; b=lJMTRVwAdBEGD6frmq64M24b4v3/Orwf8fO7B4YK2DG5luWQrN1lVo1tvYk97yw4xJ STjc74KnQWNZgp7rhAGVcySbZjoIDvKByyhRjMMPxIV75FcXnYbmu33Szb9cKVKzc9dO kzNN6WjiNEQFwKagSNaSvbyBNnraW/QqZQgyIaNpJvFW100BkcHtbpf+Ebgd0zbiG9g2 RJqsmEvhQ1hyZdEkzRLqw7u9OzFA54yY+q0YHy+KV/HepmXkIcTZjZwQam2ONI02a2Kn QGNJcczIzjCuIcu+YygLo6nguzkN9UYlM7HBOHtMIpIY9JFyCI+vbUq78gENaLnBoI7t fS2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to; bh=Y+Tt16laOOXlzdN0sH+EcFV9G9C4nIDUaWnk4FTPJ7s=; b=bI1h1qt5LdgODo55CrfecWURljCIuXRwwCrjMfxvLPUP4UkmgJRiA+grxQVud/vXiw WljZlQKiBORFODnRDsBUkhFcSFZVaL5Vm6K6RcuCWcszfw/1WvOzXU1ZA793+AMGXXVX gNaJ2uBpVnwOeIIWTNEhyxxAJMC4iEGxHZCk0KsV1SJoay/IcBTayIa4JJlQj653GQhw pcXpIzkxfR/Db7lyiChHNcL5A8cBtHYGKJAZiCV1Tg6OvENnw0KSwynSCOVW8zBZPIYV HV0Kqj0/S6cK1jFqWjYqr5Mhwink0jPQkoaadwhf5U8Q2MZAwfPRHRz+TdHX+7nhiTQp ZlJg== X-Gm-Message-State: AOAM533wj5ECoxJSl5Z5FGtpCtrJ1EBlfvuHl9EMYTBORssXGSNWaCLV hmOWR1t4U2/EQAQp3s15S77ybw== X-Google-Smtp-Source: ABdhPJxOUWtN5Tn3XUdyDZcx+wtUiPWWjgQCKH/Tb1nXqWTQQr0ujCr9bPZF6QCH3QrHYVZ3gILbLA== X-Received: by 2002:a1c:ddc3:: with SMTP id u186mr4744671wmg.72.1596561115233; Tue, 04 Aug 2020 10:11:55 -0700 (PDT) Received: from localhost (static-84-42-175-93.net.upcbroadband.cz. [84.42.175.93]) by smtp.gmail.com with ESMTPSA id 15sm4897385wmo.33.2020.08.04.10.11.50 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 04 Aug 2020 10:11:51 -0700 (PDT) Date: Tue, 4 Aug 2020 19:11:48 +0200 From: Tomas Vondra To: mailtch@163.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16569: Document "59.2. Built-in Operator Classes" have a clerical error Message-ID: <20200804171148.l3ouk6z76yblbrv6@development> References: <16569-678fd6521a12dd61@postgresql.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <16569-678fd6521a12dd61@postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Mon, Aug 03, 2020 at 03:28:27AM +0000, PG Bug reporting form wrote: >The following bug has been logged on the website: > >Bug reference: 16569 >Logged by: osdba >Email address: mailtch@163.com >PostgreSQL version: 9.5.0 >Operating system: all >Description: > >In Document "Table 59-1. Built-in GiST Operator Classes": > >"range_ops any range type && &> &< >> << <@ -|- = @> @>", > > double "@> @>", I think should be "<@ @>" . > >all version document have same clerical error. > I agree this is rather confusing, but I don't think it's a bug ... I'd bet the reason why we have '@> @>' and not '<@ @>' is that those for different argument types. GiST range_ops has @>(anyrange,anyrange) <@(anyrange,anyrange) @>(anyrange,anyelement) But we only show the first and third one, because the <@ is commutator for the first one. We have a similar thing for point_ops where we have <@ three times, but those are for different combinations of point, box and circle types. It's confusing, though. I wonder if we should do one or more of these changes: (1) include accepted argument types (2) only list distinct oprname (so not printing <@ twice) (3) include commutators (so printing both <@ and @>) (4) link to https://www.postgresql.org/docs/12/functions-range.html which already has alll these additional details regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services