Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iaKgh-0000pq-8a for pgsql-docs@arkaria.postgresql.org; Thu, 28 Nov 2019 14:22:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iaKgf-0007cf-TV for pgsql-docs@arkaria.postgresql.org; Thu, 28 Nov 2019 14:22:29 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iaKgf-0007bw-C7 for pgsql-docs@lists.postgresql.org; Thu, 28 Nov 2019 14:22:29 +0000 Received: from mail-qt1-x843.google.com ([2607:f8b0:4864:20::843]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1iaKga-0000o6-8Z for pgsql-docs@lists.postgresql.org; Thu, 28 Nov 2019 14:22:27 +0000 Received: by mail-qt1-x843.google.com with SMTP id 14so29251102qtf.5 for ; Thu, 28 Nov 2019 06:22:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=ePibRYaBmlwgrq9Lrpuf/fmfaP2NllwrJ0XjMs6HP60=; b=AgV76rbSNk9teKTaiMgESoEUF/6og/iAF4ZSn9LEi9nZ/QBWxcZ1Y6UZQ0/LjutoHy iUNR4PKwLXuBrcpXrSaiPQYH+5NVF1RDKcrzHum+9Ror8ZBjU0+BQHhKAANXufHTsejL dELK+SEprtyHiimgzRIcHH4DqycirV9M31cKRxdoQJV+UYGZ/kJS6CSIz7pMB3uqH3CI 3t2BFclazdnlo9XPxN+bwuRLhH6wuZISEtxeq8XtkPo6LNizavx8uwnzbJgSbnJCPqeI +fH9UNxnWbNqMFWaelPo9ZdcjxqYufOstXQ+sBWjpHxF+RoUIKqVGEscqwh8kZDpft9i ifQw== 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:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=ePibRYaBmlwgrq9Lrpuf/fmfaP2NllwrJ0XjMs6HP60=; b=S+Gh+w+qB64cP5ZuYA8lzGMr+6G/pr6X0h8XVY9vMQesOLdxdbdhXzacfi5uc+rOxv kwNxK3Oq/g3+lxvwiO/OEzbPL4/3AvFlvLFewFCxWMwygLeIh2rDDh9JPqol0SzLjxPD velJ0CkLB0JU2IycdHGY1MVj5gL6p7fcP11XrtIRkhkEW/BokUcb4TCbq9/x04zXTIUz lwXop9/UxJS0hb6lRxjB3anK1WNO0GEc+6upBI9F8CMtCG7cYorkzpViggAcBPtnc/z0 TQzERKz5pTmpLjj92cQXMaoHTJLJ6F3U3A0bUSN+PMojZfV26xRji7l13leEK/FqPSjS i9/Q== X-Gm-Message-State: APjAAAUTwijjCg8zHpa88WMJRGN+9CQLrfbjZdi5RYtEQvsJDvmHplx/ GlCjiUc8YGR2hqFlZA/lt4Xy45xNo9lEhw== X-Google-Smtp-Source: APXvYqzNetcK0jJZTsJmEgiH12B2uowp26f1UNQUoW/tuEd6V451GZDa/+Nxyd/8ItjU6+z1IXg3mw== X-Received: by 2002:ac8:7157:: with SMTP id h23mr7895919qtp.223.1574950942984; Thu, 28 Nov 2019 06:22:22 -0800 (PST) Received: from nimloth.alvh.no-ip.org ([179.56.96.77]) by smtp.gmail.com with ESMTPSA id 139sm2156984qkj.116.2019.11.28.06.22.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 28 Nov 2019 06:22:22 -0800 (PST) Received: by nimloth.alvh.no-ip.org (Postfix, from userid 1000) id 41770300663; Thu, 28 Nov 2019 11:22:20 -0300 (-03) Date: Thu, 28 Nov 2019 11:22:20 -0300 From: Alvaro Herrera To: Daniel Gustafsson Cc: miodrag.milic@gmail.com, pgsql-docs@lists.postgresql.org Subject: Re: Example not producing shown output Message-ID: <20191128142220.GA26485@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <0F6D5192-31DE-4BB0-9FF1-F8BC268C10AE@yesql.se> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2019-Nov-27, Daniel Gustafsson wrote: > > On 26 Nov 2019, at 19:28, Alvaro Herrera wrote: > > > Or perhaps we can add a second line in the example cell for the > > @@ operator, to make it clear that both forms can be used. Users can be > > expected to apply some intuition from that point onwards. > > Wouldn't it be more intuitive to add such a second line under to_tsvector, or > expand the Description field to cover a brief discussion covering this? I don't know. The problem is that the line for to_tsvector is a lot further down the page in table 9.42, and it contains a lot of other stuff, so people trying their first examples based on table 9.41 would not see it and will be as surprised as the OP was when it doesn't work under their locale. I think enlarging the description for the @@ entry is not out of the question, but trying to explain too much about the locale there seems a bit out of place. This is why I suggested to add another Note box below the table. If I misunderstood what you meant, please be more specific. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services