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 1t0TXZ-00BdhR-VJ for pgsql-general@arkaria.postgresql.org; Mon, 14 Oct 2024 22:27:49 +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 1t0TXY-000TRH-52 for pgsql-general@arkaria.postgresql.org; Mon, 14 Oct 2024 22:27:48 +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 1t0TXX-000TR8-Pn for pgsql-general@lists.postgresql.org; Mon, 14 Oct 2024 22:27:48 +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.94.2) (envelope-from ) id 1t0TXV-000uCA-IU for pgsql-general@lists.postgresql.org; Mon, 14 Oct 2024 22:27:46 +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 49EMRfpl3836256; Mon, 14 Oct 2024 18:27:41 -0400 From: Tom Lane To: Zac Warham cc: Adrian Klaver , "pgsql-general@lists.postgresql.org" Subject: Re: Changing postgres User In-reply-to: References: <685640e7-4533-4483-acfc-d8dc60de5515@aklaver.com> Comments: In-reply-to Zac Warham message dated "Mon, 14 Oct 2024 22:09:59 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3836254.1728944861.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Mon, 14 Oct 2024 18:27:41 -0400 Message-ID: <3836255.1728944861@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Zac Warham writes: > Thank you for the link to the documentation however it is the UID and GI= D of 1001:1001 that is required, not the username which I believe this is = intended for? Is there a similar option for UID and GID? Apologies if my o= riginal question was not clear in this manner. The underlying UID/GID will necessarily be that of the OS account that is running initdb. I don't see why you need to worry about it. If you don't want the Postgres role name of the initial superuser role to be the same as the OS account's name, you can select something else using the switch Adrian mentioned --- but that's really mostly cosmetic. It has nothing to do with OS-level privileges. regards, tom lane