Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1eezkA-0008In-1r
	for pgsql-docs@arkaria.postgresql.org; Fri, 26 Jan 2018 08:52:18 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1eezk8-0003aS-Tf
	for pgsql-docs@arkaria.postgresql.org; Fri, 26 Jan 2018 08:52:16 +0000
Received: from makus.postgresql.org ([2001:4800:1501:1::229])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.84_2)
	(envelope-from <gptmailinglists@gmail.com>)
	id 1eezk8-0003aI-I8
	for pgsql-docs@lists.postgresql.org; Fri, 26 Jan 2018 08:52:16 +0000
Received: from mail-qt0-x242.google.com ([2607:f8b0:400d:c0d::242])
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <gptmailinglists@gmail.com>)
	id 1eezk1-0002Ub-4M
	for pgsql-docs@postgresql.org; Fri, 26 Jan 2018 08:52:15 +0000
Received: by mail-qt0-x242.google.com with SMTP id g14so25977614qti.2
        for <pgsql-docs@postgresql.org>; Fri, 26 Jan 2018 00:52:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc;
        bh=qDTCrY8CMsuHjpobGyRMBtFyo0CKy/7YdmpSYRIytIY=;
        b=C5GxRwB9SMhVtLvYI958egozAoGW7TQklPfUxi83QMSFOTNLL/WYj+Mfqhp+9QzG9q
         Fri+yBKt8CZejohEfi6C2n/Lcq5Zkv4sh91nNDVHw7q/mZWSZJDrDbbVoacv+Vu+45zI
         tYJUGF9CLEkvS9S3idIbl7NruPtW2gpmRjGMhMp6UUNQcWQKFukywWQP0S9/bTOn6SBr
         Bz32d19sX/SvMMJb5NE0F0JM+KTm4b/u9uV4P4GzUms49Io9IZxivCEXyeOswFenVvev
         Rc8u1FTerY4QrfkxQ+SpeUvq2w8NuebcLjx3P+zhOLsPIK1IzKIYQX2T3mu1f5b4aXYV
         7HSg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:in-reply-to:references:from:date
         :message-id:subject:to:cc;
        bh=qDTCrY8CMsuHjpobGyRMBtFyo0CKy/7YdmpSYRIytIY=;
        b=au92x1i6ve6AM8XStv1GgoBwInGnbtXoFjEYWKVg93HoDE6vrlsyGocEtwYuUEqCFR
         Y7cW9yE7S/qNrs4nX37vDAdQ2E8mh54bszCv3syhliCAnXpX0DjItqJeNc+j1B5Y8XZO
         TsTJLXg5uKF8qPwX5grk5DDJ9a4YFo1orYwRx7zl9XGpnjc+mDAyB+ynHDg3Aho4usGI
         iCAqbFGh0i32idQL4jCkRrDKyFOuYdkfhZ1wWD6NE6CJ2gjyGyx1CC/dYRKZHSakhUd1
         ZHZn7PhE75ENlBikzNG+3/3H3YO9Mma7SSLYjeCwO7qKR6nCfPvLmbTa3/9nBqVmBHJO
         KoYA==
X-Gm-Message-State: AKwxytenn129B6IFhox0dTMYuItTaVX6NFvB22/fyUhGzZfE0SR+Xoqc
	XKZRr8n9sVxWH3eC+wiSmgOcmvbl4it+hDSWeY4=
X-Google-Smtp-Source: 
 AH8x227exq0qbIKXnmGF9pXnYhoTqhqO/wt+8cWUQrUTaEBsZwtvR7wyROnUFUKCMN9NWbrytt6zzdJr2bOfiC2a2s8=
X-Received: by 10.200.53.79 with SMTP id z15mr22253879qtb.278.1516956727852;
 Fri, 26 Jan 2018 00:52:07 -0800 (PST)
MIME-Version: 1.0
Received: by 10.12.146.11 with HTTP; Fri, 26 Jan 2018 00:52:07 -0800 (PST)
In-Reply-To: <20180125225523.GB22736@momjian.us>
References: <20171214093339.29863.34708@wrigleys.postgresql.org>
 <20180125225523.GB22736@momjian.us>
From: GPT <gptmailinglists@gmail.com>
Date: Fri, 26 Jan 2018 09:52:07 +0100
Message-ID: 
 <CADep2PMy2cVifjYgnDoxRsT7CESQ1v4a1sTAUkPPBtcOap4JEg@mail.gmail.com>
Subject: Re: Addition to / Clarification in 9.7.1. LIKE
To: Bruce Momjian <bruce@momjian.us>
Cc: pgsql-docs@postgresql.org
Content-Type: text/plain; charset="UTF-8"
List-Id: <pgsql-docs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-docs@lists.postgresql.org>
List-Owner: <mailto:pgsql-docs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-docs>
Precedence: bulk

Between 1st (The LIKE expression...) and 2nd (If pattern does not...)
paragraphs, it could be added something like:

<begin>
                                               Caution
Contrary to some other databases, in Postgresql only two characters
are used in LIKE patterns: underscore (_) and percent sign (%).
The use of any other character will lead to an error.
<end>

The error message also would be more clarified to inform user about
the use of not supported characters.

On 1/25/18, Bruce Momjian <bruce@momjian.us> wrote:
> On Thu, Dec 14, 2017 at 09:33:39AM +0000, gptmailinglists@gmail.com wrote:
>> The following documentation comment has been logged on the website:
>>
>> Page: https://www.postgresql.org/docs/10/static/functions-matching.html
>> Description:
>>
>> Between the 1st and 2nd paragraphs please add a new one which make clear
>> (also to a newbie like myself) that the _only characters_ can be used in
>> pattern are (_) and (%).
>
> Uh, it is not totally clear what you are suggesting here.  I think you
> are talking about the LIKE command and its use of _ and %.  What detail
> should be added?  Can you show an example?
>
> --
>   Bruce Momjian  <bruce@momjian.us>        http://momjian.us
>   EnterpriseDB                             http://enterprisedb.com
>
> + As you are, so once was I.  As I am, so you will be. +
> +                      Ancient Roman grave inscription +
>