| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | 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-13 19:49:30 |
| Message-ID: | 443431.1752436170@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2025-07-13 21:11:14 | Re: please define 'statement' in the glossary |
| Previous Message | David G. Johnston | 2025-07-13 19:27:09 | Re: correction suggestion for https://www.postgresql.org/docs/17/auth-username-maps.html |