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 1uY6mK-001Cek-11 for pgsql-hackers@arkaria.postgresql.org; Sat, 05 Jul 2025 17:34:20 +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 1uY6mH-008Pg2-UH for pgsql-hackers@arkaria.postgresql.org; Sat, 05 Jul 2025 17:34:18 +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 1uY6mH-008Pej-Kc for pgsql-hackers@lists.postgresql.org; Sat, 05 Jul 2025 17:34:18 +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 1uY6mG-005kCg-1u for pgsql-hackers@lists.postgresql.org; Sat, 05 Jul 2025 17:34:17 +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 565HYDaY010701; Sat, 5 Jul 2025 13:34:13 -0400 From: Tom Lane To: Jianghua Yang cc: Peter Eisentraut , pgsql-hackers@lists.postgresql.org Subject: Re: [PATCH] initdb: Treat empty -U argument as unset username In-reply-to: References: <3793879.1751492926@sss.pgh.pa.us> Comments: In-reply-to Jianghua Yang message dated "Sat, 05 Jul 2025 09:58:09 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <10699.1751736853.1@sss.pgh.pa.us> Date: Sat, 05 Jul 2025 13:34:13 -0400 Message-ID: <10700.1751736853@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Jianghua Yang writes: > I wanted to ask if this patch can be merged first, as it seems to be a > separate issue different from the aclitem parsing problem Tom discussed in > https://www.postgresql.org/message-id/3792884.1751492172%40sss.pgh.pa.us Merging your patch will make it more difficult to poke at these underlying issues, so I'm not in a hurry to do that. It's not like this is an urgent issue: initdb has behaved like that for years if not decades, and nobody's complained before. regards, tom lane