Date: Mon, 26 Jul 2021 22:55:25 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: troy@frericks.us, pgsql-docs@lists.postgresql.org
Subject: Re: Manua correction
Message-ID: <20210727025525.GC19774@momjian.us>
References: <162614304115.701.2392941350859387646@wrigleys.postgresql.org>
 <20210715213623.GC14027@momjian.us>
 <3701102.1626405158@sss.pgh.pa.us>
 <20210719142355.GA12687@momjian.us>
 <400208.1626793389@sss.pgh.pa.us>
 <20210720200617.GA27025@momjian.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20210720200617.GA27025@momjian.us>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: 
 <https://www.postgresql.org/message-id/20210727025525.GC19774%40momjian.us>
Precedence: bulk

On Tue, Jul 20, 2021 at 04:06:17PM -0400, Bruce Momjian wrote:
> On Tue, Jul 20, 2021 at 11:03:09AM -0400, Tom Lane wrote:
> > The places where you changed "substring(s)" to "substrings" are maybe
> > not flat wrong, but I don't think they're improving the text either.
> > IIRC, in most of them you get one match if you didn't use the 'g'
> > flag, but possibly multiple matches if you did, and the "substring(s)"
> > wording is meant to allude to that without taking the space to spell
> > it out explicitly.
> 
> I see what you mean --- there can be multiple capture groups, and
> multiple match processing if 'g' is used.  I think the text using "(s)"
> is too complex, so I spelled out the use 'g' and clarified the case of
> multiple groups in a single regex.
> 
> Updated patch attached, and I used a larger line context around the
> changes to clarify what was being modified.

Patch applied back to PG 13 --- before that, the text supplied as much
more minimal.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  If only the physical world exists, free will is an illusion.