From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | alexey(dot)shishkin(at)enterprisedb(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: correction suggestion for https://www.postgresql.org/docs/17/auth-username-maps.html |
Date: | 2025-07-09 15:15:09 |
Message-ID: | CAKFQuwbhZg8C93_GU0WP=3qGuT0kbPsLL1htP-svrv=Bgjkpeg@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Wed, Jul 9, 2025 at 7:56 AM PG Doc comments form <noreply(at)postgresql(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2025-07-09 16:22:07 | Re: correction suggestion for https://www.postgresql.org/docs/17/auth-username-maps.html |
Previous Message | PG Doc comments form | 2025-07-09 12:06:33 | correction suggestion for https://www.postgresql.org/docs/17/auth-username-maps.html |