Re: correction suggestion for https://www.postgresql.org/docs/17/auth-username-maps.html - Mailing list pgsql-docs

From David G. Johnston
Subject Re: correction suggestion for https://www.postgresql.org/docs/17/auth-username-maps.html
Date
Msg-id CAKFQuwbhZg8C93_GU0WP=3qGuT0kbPsLL1htP-svrv=Bgjkpeg@mail.gmail.com
Whole thread Raw
In response to correction suggestion for https://www.postgresql.org/docs/17/auth-username-maps.html  (PG Doc comments form <noreply@postgresql.org>)
Responses Re: correction suggestion for https://www.postgresql.org/docs/17/auth-username-maps.html
List pgsql-docs
On Wed, Jul 9, 2025 at 7:56 AM PG Doc comments form <noreply@postgresql.org> wrote:
The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/17/auth-username-maps.html
Description:

Dear all,
Pls. let me suggest the correction for the
https://www.postgresql.org/docs/17/auth-username-maps.html page.
It has the following sentence:
'
If the database-username field starts with a slash (/), the remainder of the
field is treated as a regular expression (see Section 9.7.3.1 for details of
PostgreSQL's regular expression syntax). It is not possible to use \1 to use
a capture from regular expression on system-username for a regular
expression on database-username.
'
It looks like 'to use a capture' has to be replaced by 'to capture'.
best regards

What is written is factually correct.  Your suggestion makes it incorrect; and wouldn't be good English even if it was.
"to capture" involves (...) while using said capture involves \#

David J.

pgsql-docs by date:

Previous
From: PG Doc comments form
Date:
Subject: correction suggestion for https://www.postgresql.org/docs/17/auth-username-maps.html
Next
From: Tom Lane
Date:
Subject: Re: correction suggestion for https://www.postgresql.org/docs/17/auth-username-maps.html