Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ub2hd-00D1G9-GQ for pgsql-docs@arkaria.postgresql.org; Sun, 13 Jul 2025 19:49:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1ub2hb-000bWs-EP for pgsql-docs@arkaria.postgresql.org; Sun, 13 Jul 2025 19:49:36 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ub2hb-000bU9-6K for pgsql-docs@lists.postgresql.org; Sun, 13 Jul 2025 19:49:35 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1ub2ha-0077Ot-0l for pgsql-docs@lists.postgresql.org; Sun, 13 Jul 2025 19:49:34 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 56DJnUkT443432; Sun, 13 Jul 2025 15:49:30 -0400 From: Tom Lane To: "David G. Johnston" cc: alexey.shishkin@enterprisedb.com, pgsql-docs@lists.postgresql.org Subject: Re: correction suggestion for https://www.postgresql.org/docs/17/auth-username-maps.html In-reply-to: References: <175206279327.3157504.12519088928605422253@wrigleys.postgresql.org> <1145313.1752078127@sss.pgh.pa.us> <1341070.1752089404@sss.pgh.pa.us> <1409232.1752098746@sss.pgh.pa.us> <435403.1752431413@sss.pgh.pa.us> Comments: In-reply-to "David G. Johnston" message dated "Sun, 13 Jul 2025 12:27:09 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <443430.1752436170.1@sss.pgh.pa.us> Date: Sun, 13 Jul 2025 15:49:30 -0400 Message-ID: <443431.1752436170@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk "David G. Johnston" 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