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 1jaRqZ-0000RN-7i for pgsql-docs@arkaria.postgresql.org; Sun, 17 May 2020 22:33:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jaRqY-0004kg-3P for pgsql-docs@arkaria.postgresql.org; Sun, 17 May 2020 22:33:26 +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 1jaRqX-0004kZ-Tu for pgsql-docs@lists.postgresql.org; Sun, 17 May 2020 22:33:25 +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 1jaRqV-0003C8-UY for pgsql-docs@lists.postgresql.org; Sun, 17 May 2020 22:33:24 +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 04HMXLp6017937; Sun, 17 May 2020 18:33:21 -0400 From: Tom Lane To: b@janin.com cc: pgsql-docs@lists.postgresql.org Subject: Re: non-string or non-string In-reply-to: <158974990906.7031.8787889795019651207@wrigleys.postgresql.org> References: <158974990906.7031.8787889795019651207@wrigleys.postgresql.org> Comments: In-reply-to PG Doc comments form message dated "Sun, 17 May 2020 21:11:49 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <17935.1589754801.1@sss.pgh.pa.us> Date: Sun, 17 May 2020 18:33:21 -0400 Message-ID: <17936.1589754801@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk PG Doc comments form writes: > The second line in "Table 9.8. SQL String Functions and Operators" uses > "non-string or non-string" as part of the example. I assume one of these > should be "string". It might look that way depending on how wide your browser window is... but the way it's supposed to be read is string || non-string or non-string || string The devel version of the docs forces the two cases to be on separate lines, which hopefully will stem the confusion. regards, tom lane