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 1jaRor-0000P2-9t for pgsql-docs@arkaria.postgresql.org; Sun, 17 May 2020 22:31:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jaRoo-0002sU-NN for pgsql-docs@arkaria.postgresql.org; Sun, 17 May 2020 22:31:38 +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 1jaRoo-0002pi-BV for pgsql-docs@lists.postgresql.org; Sun, 17 May 2020 22:31:38 +0000 Received: from mail-qv1-xf44.google.com ([2607:f8b0:4864:20::f44]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jaRol-0004IK-0n for pgsql-docs@lists.postgresql.org; Sun, 17 May 2020 22:31:37 +0000 Received: by mail-qv1-xf44.google.com with SMTP id z5so3864874qvw.4 for ; Sun, 17 May 2020 15:31:34 -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:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=FFhpdhLN4Gvk+X7VmOD5kypb1ztqL9ticlJ8No9JOcA=; b=HGK3IDgwMFh0iW5fJWUgFBFnhSXH6SOoFi7JKvmQAwZoxungIWLJzcnuVSV0+WABW6 4CGwQRoHgxAtLUjc4qx2GrKHJHy4EpyE3AhlCYSxWBnFJQEpPNRIFBUzOBk/cRqhAMaz Nu0TFGQHhgaz7m+QmVOglQFSPmMy+BNwhBxQ3zrV8HqsptXdnibBMXoG3mhZL/vcBKYF xB/rrkEmy40E0ZBoD/v0hRiIJ6wirdysRpqPjvOm3EyVwmeih+0jg1bgRsPKS/J4ZoJ8 SylTd2OpPBuZbH8oNOF5Zr9bQJpV1TYRWfHe0xmvEQwklHc74ntJCfJbXFvkx2dQy/cm 3nOg== 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:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=FFhpdhLN4Gvk+X7VmOD5kypb1ztqL9ticlJ8No9JOcA=; b=aLEtRr81334jZS7hUDprHSDfHBUyauVrLoamhxuOisOf646hUt9geuNnlfmsMQ/sBQ KR0XKWvYaAXZ348WNE2vfs9lZ/XaDvAQdQaCPV5sCbYUexY2qqjUOFk4KUEE137eR6H+ aQ6sOSIT/hF0TxvcjEbix+e3tinYXHc4FMFhFptxOoVAzNVZzznJzB2wzR9nYEByRHZu k5aqI/zHH2VCRZmvJuCrHJAqjNQngak/irpyu/IhLWR5y0dNb0f923lCVZN1vx32Rkx2 9TiCDtHlqRUrO6rHYVlBWGxLXoRbHb+Edtepn9PkzjlDuHh8iSmxEhNw5P/MgtdeTcPE 7Wow== X-Gm-Message-State: AOAM533ASUt6vsxMYNfUlGQ9rrYDuMGwyNlZ5ZHcd97rEtYtkYInq0WX 4zgiJgi/32KWsbjacWuV6s6Aow== X-Google-Smtp-Source: ABdhPJxAGnrj07xLXQZvKl8YLGTLrQ/lEXrDah9442/cDncPJ9/I1sADvyY0fZFItVThSYY5QU82Mw== X-Received: by 2002:a0c:ee64:: with SMTP id n4mr12933246qvs.246.1589754692311; Sun, 17 May 2020 15:31:32 -0700 (PDT) Received: from nimloth.alvh.no-ip.org ([190.95.18.252]) by smtp.gmail.com with ESMTPSA id f198sm7025584qke.46.2020.05.17.15.31.30 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 17 May 2020 15:31:31 -0700 (PDT) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id E0E0E300712; Sun, 17 May 2020 18:31:28 -0400 (-04) Date: Sun, 17 May 2020 18:31:28 -0400 From: Alvaro Herrera To: b@janin.com, pgsql-docs@lists.postgresql.org Subject: Re: non-string or non-string Message-ID: <20200517223128.GA8607@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <158974990906.7031.8787889795019651207@wrigleys.postgresql.org> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2020-May-17, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/11/functions-string.html > Description: > > 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". No, it's not the example but the operator description, and what it says is "string || non-string or non-string || string" so it's trying to illustrate that there are two options: string || non-string non-string || string but maybe it's not super-clear about that. This is much clearer in the docs for Postgres 13, which has been heavily reformatted: https://www.postgresql.org/docs/devel/functions-string.html -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services