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-13T19:49:30Z
Lists: pgsql-docs
"David G. Johnston" <david.g.johnston@gmail.com> writes: > (Likewise, the system-username regexp can contain more than one capture - > which are only available later in the system-username regexp - though again > it seems unlikely anyone is going to use that feature in this context.) Yeah, I was thinking about that while working on the multiple-\1 patch. Sooner or later somebody is going to ask why they can't use \2, \3, etc in the database-username. I think it would be a pretty minor finger exercise to make the new code do that, but I refrained for now. > I'm good with this. Cool. I'll push after the beta2 release freeze lifts. 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