Re: correction suggestion for https://www.postgresql.org/docs/17/auth-username-maps.html
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: alexey.shishkin@enterprisedb.com, pgsql-docs@lists.postgresql.org
Date: 2025-07-09T16:22:07Z
Lists: pgsql-docs
"David G. Johnston" <david.g.johnston@gmail.com> writes: > On Wed, Jul 9, 2025 at 7:56 AM PG Doc comments form <noreply@postgresql.org> > wrote: >> 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. The existing sentence is pretty mangled English, though. I think it would be clearer as When the database-username field is a regular expression, it is not possible to use \1 within it to refer to a capture from the system-username field. Thoughts? regards, tom lane
Commits
-
Doc: clarify description of regexp fields in pg_ident.conf.
- ff6783ce5260 16.10 landed
- f8ce5dea433c 18.0 landed
- dc70816fde6e 13.22 landed
- b70a2e8a1a0d 17.6 landed
- 6f7d016e917e 14.19 landed
- 5fe55a0fe40e 19 (unreleased) landed
- 2132ced7dc97 15.14 landed
-
In username-map substitution, cope with more than one \1.
- 3c4e26a62c31 19 (unreleased) landed