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 1jROvM-0006YE-1j for pgsql-docs@arkaria.postgresql.org; Wed, 22 Apr 2020 23:37:00 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jROvK-0007wz-V3 for pgsql-docs@arkaria.postgresql.org; Wed, 22 Apr 2020 23:36:58 +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 1jROvK-0007ws-Pk for pgsql-docs@lists.postgresql.org; Wed, 22 Apr 2020 23:36:58 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jROvI-0004at-BU for pgsql-docs@lists.postgresql.org; Wed, 22 Apr 2020 23:36:57 +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 03MNassE009457; Wed, 22 Apr 2020 19:36:54 -0400 From: Tom Lane To: "David G. Johnston" cc: "Strauss, Randy (ARC-AF)[SGT, INC]" , "pgsql-docs@lists.postgresql.org" Subject: Re: Lack of detailed documentation In-reply-to: <27125.1581367420@sss.pgh.pa.us> References: <158110996889.1089.4224139874633222837@wrigleys.postgresql.org> <6537.1581264535@sss.pgh.pa.us> <3D8A56AB-AC13-46D7-B72B-B913A4ACDA7D@nasa.gov> <27125.1581367420@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Mon, 10 Feb 2020 15:43:40 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <9455.1587598614.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Wed, 22 Apr 2020 19:36:54 -0400 Message-ID: <9456.1587598614@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk I wrote: > One thing that's sort of blocking any real progress on this is the > draconian space constraints imposed by the tabular format, which is > hurting us on a lot of these pages, not just this one. Alvaro did > some preliminary investigation towards finding a better way, > but nobody's tried to push that forward. I've been making an attempt to improve that situation, and along the way just pushed an expansion of the geometric-operator docs: https://www.postgresql.org/docs/devel/functions-geometry.html There's probably still some things to be desired, but it's a lot less fuzzy than before. One thing that surprised me is that I couldn't find any well-known name for what the * and / operators are doing; digging around on the net and in some dusty old math textbooks didn't yield any exact matches. I ended up adding footnotes with the actual computations, but I'm not very happy with that approach. Surely Lockhart[1] got this definition from someplace, though, and didn't invent it out of thin air. regards, tom lane [1] I'd supposed we could blame this stuff on Berkeley, but excavation in our git history shows it came in at https://git.postgresql.org/gitweb/?p=3Dpostgresql.git&a=3Dcommitdiff&h=3D9= e2a87b62db87fc4175b00dabfd26293a2d072fa ... sans documentation of course.