Re: correction suggestion for https://www.postgresql.org/docs/17/auth-username-maps.html - Mailing list pgsql-docs

From David G. Johnston
Subject Re: correction suggestion for https://www.postgresql.org/docs/17/auth-username-maps.html
Date
Msg-id CAKFQuwZu6kZ8ZPvJ3pWXig+6UX4nTVK-hdL_ZS3fSdps=RJQQQ@mail.gmail.com
Whole thread Raw
In response to Re: correction suggestion for https://www.postgresql.org/docs/17/auth-username-maps.html  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: correction suggestion for https://www.postgresql.org/docs/17/auth-username-maps.html
List pgsql-docs
On Wed, Jul 9, 2025 at 9:22 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
"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:

The existing sentence is pretty mangled English, though.

Agreed.


  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?

Its good as far a narrow fix goes.

But how about the attached?  More invasive but covers the salient points better, IMO, and less repetitive than having the two fields have their own basically copy-pasted paragraphs.

I didn't add an example but felt the point "be referenced a single time within" to be needed since, usefulness not withstanding, writing \1\1 for database-username works but only the first instance of \1 is replaced.

Also, should we attempt to align this documentation and pg_ident.conf.sample as pertains to pg-username vs. database-username?

David J.

Attachment

pgsql-docs by date:

Previous
From: Tom Lane
Date:
Subject: Re: correction suggestion for https://www.postgresql.org/docs/17/auth-username-maps.html
Next
From: Tom Lane
Date:
Subject: Re: correction suggestion for https://www.postgresql.org/docs/17/auth-username-maps.html