correction suggestion for https://www.postgresql.org/docs/17/auth-username-maps.html
The Post Office <noreply@postgresql.org>
From: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: alexey.shishkin@enterprisedb.com
Date: 2025-07-09T12:06:33Z
Lists: pgsql-docs
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 Alexey Shishkin
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